On Thu, 24 Jan 2002, Richard Levitte - VMS Whacker wrote:
If we retain the old symbols in the library, which is currently
expected, they don't need to recompile. Re*linking* would be
sufficient to satisfy the linkers idea of what the program needs.
I don't think anyone will be too upset
Richard Levitte - VMS Whacker wrote:
From: Lutz Jaenicke [EMAIL PROTECTED]
Lutz.Jaenicke On Wed, Jan 23, 2002 at 11:21:49AM -0800, Booker C. Bense wrote:
Lutz.Jaenicke - I was afraid you'd say that... It defeats the whole
Lutz.Jaenicke point of changing the names in the first place[1].
On Thu, 24 Jan 2002, Richard Levitte - VMS Whacker wrote:
My first attepmt was to do the whole thing with cpp macros. However,
after giving it some thought, that could cause a number of problems;
one is that macros have zero type safety. You can give those macros
exactly whatever without
From: Jeffrey Altman [EMAIL PROTECTED]
jaltman The only way that this can be handled is to use macros to map from
jaltman the old api to the new functions. I do not see any other way that
jaltman will allow the libdes.a to be mixed with libcrypto.a.
I'm thinking you're right. At the same
From: Ben Laurie [EMAIL PROTECTED]
ben But, this isn't the end of the story. On some architectures, there
ben are binary incompatibilities between openssl's libcrypto and libdes.
ben
ben Arg!
Hardly a surprise, I've talked about that before (last summer or
autumn, IIRC). The
From: Richard Levitte - VMS Whacker [EMAIL PROTECTED]
levitte I'm thinking you're right. At the same time, I want to retain C type
levitte security as well as possible. How about this: I could rename all the
levitte old functions to _old_des_* and then have cpp macros that map des_* to
levitte
From: Jeffrey Altman [EMAIL PROTECTED]
jaltman The only way that this can be handled is to use macros to map from
jaltman the old api to the new functions. I do not see any other way that
jaltman will allow the libdes.a to be mixed with libcrypto.a.
I'm thinking you're right. At the
On Wed, Jan 23, 2002 at 11:21:49AM -0800, Booker C. Bense wrote:
On Wed, 23 Jan 2002, Lutz Jaenicke wrote:
On Wed, Jan 23, 2002 at 07:03:20AM -0800, Booker C. Bense wrote:
On Wed, 23 Jan 2002, Lutz Jaenicke wrote:
Ok, the behaviour of the OpenSSL-0.9.7 has been adjusted:
The old
From: Lutz Jaenicke [EMAIL PROTECTED]
Lutz.Jaenicke On Wed, Jan 23, 2002 at 11:21:49AM -0800, Booker C. Bense wrote:
Lutz.Jaenicke - I was afraid you'd say that... It defeats the whole
Lutz.Jaenicke point of changing the names in the first place[1]. Oh
Lutz.Jaenicke well, I'll just have to
From: Damien Miller [EMAIL PROTECTED]
djm On Thu, 24 Jan 2002, Richard Levitte - VMS Whacker wrote:
djm
djm My first attepmt was to do the whole thing with cpp macros. However,
djm after giving it some thought, that could cause a number of problems;
djm one is that macros have zero type
djm The other problem is applications
djm that link either with libdes or with openssl's libcrypto. The latter
djm will very suddenly fail.
djm
djm How? These apps would need to be recompiled anyway - that way they would
djm pick up the macros.
If we retain the old symbols in the
On Thu, Jan 24, 2002 at 02:32:24AM -0500, Jeffrey Altman wrote:
djm The other problem is applications
djm that link either with libdes or with openssl's libcrypto. The latter
djm will very suddenly fail.
djm
djm How? These apps would need to be recompiled anyway - that way they
12 matches
Mail list logo
