OpenSSH and OpenSSL snapshots
Ben Laurie
ben at algroup.co.uk
Thu Jan 24 19:34:41 EST 2002
Richard Levitte - VMS Whacker wrote:
>
> From: Lutz Jaenicke <Lutz.Jaenicke at aet.TU-Cottbus.DE>
>
> 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 figure a way to install
> Lutz.Jaenicke> > openssl without them. At least you tried to do the
> Lutz.Jaenicke> > right thing.
> Lutz.Jaenicke> >
> Lutz.Jaenicke> > - BTW, the cpp macro trick works. I've used it in the
> Lutz.Jaenicke> > kerberos code to allow openssl compatiblity. Looks
> Lutz.Jaenicke> > like I'll have to keep those patches around.
> Lutz.Jaenicke> >
> Lutz.Jaenicke> > - Booker C. Bense
> Lutz.Jaenicke> >
> Lutz.Jaenicke> > [1] Unless you put them in separate library.
>
> 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 the compiler reacting, since a lot of casts
> would be made in their expansion.
Umm ... but we know how to do typesafe macros, remember?
> The other problem is applications
> that link either with libdes or with openssl's libcrypto. The latter
> will very suddenly fail.
Not sure what to do about this one, though!
> But, this isn't the end of the story. On some architectures, there
> are binary incompatibilities between openssl's libcrypto and libdes.
Arg!
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html http://www.thebunker.net/
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
More information about the openssh-unix-dev
mailing list