I had to add a semicolon between fi and done in the install: target
of the main make file to avoid a shell syntax error failure (unexpected
token done).
I see the problem in the current snapshot.
My shell is Bash 2.00.
--
Bryan HendersonPhone 408-621-2000
The main make file does not use INSTALL_PREFIX in installing some of
the files in OPENSSLDIR. My understanding of INSTALL_PREFIX is that I
don't want anything installed on the build system -- just put somewhere
where I can scoop it up and install it somewhere separately.
Along these same lines,
Hello,
I am using openssl_0.9.6a.
Following code has been used to convert a PKCS 12 cert to PEM format. But I am getting
some memory leaks reported. The report is listed at the end also.
Anyone has any ideas? I ran the same piece of code through Purify, same leak
reported. From there, I can
I had to add a semicolon between fi and done in the install: target
of the main make file to avoid a shell syntax error failure (unexpected
token done).
I see the problem in the current snapshot.
My shell is Bash 2.00.
--
Bryan HendersonPhone 408-621-2000
The main make file does not use INSTALL_PREFIX in installing some of
the files in OPENSSLDIR. My understanding of INSTALL_PREFIX is that I
don't want anything installed on the build system -- just put somewhere
where I can scoop it up and install it somewhere separately.
Along these same
Is there any chance that somone will comment on this topic anytime
soon ?
PT Does the attached oneliner make sense ? IMO it doesnt break anything,
PT but allows reusing the EVP_CIPHER_CTX in calls to EVP_EncryptUpdate,
PT after EVP_EncryptFinal is called.
PT Any comments greatly appreciated :)
I'm not on the dev team or anything, but I don't understand how you could have *ever*
successfully encrypted multiple streams with the same EVP context??? Just the IV's
alone would have been screwed up for CBC ciphers and stream ciphers like RC4 would
completely break.
Unless, of course, you
Hello Lee,
Friday, May 03, 2002, 4:21:04 PM, you wrote:
DL I'm not on the dev team or anything, but I don't understand how you could have
*ever* successfully encrypted multiple streams with the same EVP context??? Just the
IV's alone would have been
DL screwed up for CBC ciphers and stream
So, I need to know the process of integration of new cipher to Crypto
library.
I've tried to place the directory with new cipher (aes) inside of the
crypto
directory,
modified root Makefile.ssl and crypto/Makefile.ssl however it seems that
it
is not enough -
new codec does not
DL I'm not on the dev team or anything, but I don't understand how you could have
*ever* successfully encrypted multiple streams with the same EVP context??? Just the
IV's alone would have been
DL screwed up for CBC ciphers and stream ciphers like RC4 would completely break.
PT ECB won't - IV
Hello James,
Right now I was writing a letter to you with the question regarding
integration of openvpn and openssl 0.9.7 .:).
I'll be glad to receive such patch because I need to integrate AES algorithm
to openvpn
(my boss requested this).
Thanks, in advance.
Ildar.
PS.
Is the patch only for
From: James Yonan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Copies to: [EMAIL PROTECTED]
Subject:OpenVPN and OpenSSL 0.9.7 was: Re: Integration of
AES algorith to OpenSSL Crypto library
Date sent: Fri, 3 May 2002
On Fri, May 03, 2002 at 09:09:01AM -0600, James Yonan wrote:
So, I need to know the process of integration of new cipher to Crypto
library.
I've tried to place the directory with new cipher (aes) inside of the
crypto
directory,
modified root Makefile.ssl and crypto/Makefile.ssl
I know this may sound simplistic, but since you are the author of
OpenVPN, why don't you make a simple check for the OpenSSL version
and use 0.9.7 the way it was designed to be used. If the check
indicates you are using 0.9.6, use the method you currently use.
Actually OpenVPN 1.1.1 already
Hi,
unfortunately openssl-0.9.6d-beta1 won´t compile on my system. I have this
strange feeling that it´s because of my gcc:
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: /usr/local/src/gcc/gcc_3.1.x/configure
--enable-languages=c,c++Thread model: single
On Fri, May 03, 2002 at 10:01:52PM +0200, Axel H. Siebenwirth wrote:
unfortunately openssl-0.9.6d-beta1 won?t compile on my system. I have this
strange feeling that it?s because of my gcc:
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with:
Hi Lutz!
On Fri, 03 May 2002, Lutz Jaenicke wrote:
On Fri, May 03, 2002 at 10:01:52PM +0200, Axel H. Siebenwirth wrote:
unfortunately openssl-0.9.6d-beta1 won?t compile on my system. I have this
strange feeling that it?s because of my gcc:
Reading specs from
Experimenting with openssl smime -decrypt, I found that it did not detect that a
message was truncated. Changing line 173 of crypto/asn1/a_d2i_fp.c from
if (i = 0)
to
if (i want)
fixes the problem. I think this is the right code for all cases, but somebody who
actually understands the
18 matches
Mail list logo
