This is a discussion on Re: [PATCH] Remove old libdes support? - Openssl ; In message on Mon, 20 Mar 2006 02:15:15 -0700, "Kyle Hamilton" said: aerowolf> On 3/19/06, Ted Mittelstaedt wrote: aerowolf> > aerowolf> > aerowolf> > >I think we have 2 options: aerowolf> > >- Completly drop the old des support, including ...
In message <6b9359640603200115q6e67b6ecr682e1b9328244bca@mail. gmail.com> on Mon, 20 Mar 2006 02:15:15 -0700, "Kyle Hamilton"
aerowolf> On 3/19/06, Ted Mittelstaedt
aerowolf> > >I think we have 2 options:
aerowolf> > >- Completly drop the old des support, including des_old.h
aerowolf> > >- Drop the libdes compatibility, so that it's only compatible
aerowolf> > > with older openssl versions, and people can still use the des_*
aerowolf> > > versions.
aerowolf> > >
aerowolf> > How about option 3 - change the default to not include it but
aerowolf> > leave the code still in there, then see how many people
aerowolf> > squawk about old des support "missing" and get told to
aerowolf> > set the flag to include it, then make a decision about
aerowolf> > stripping it out completely, based on that.
aerowolf> My personal opinion is that if there's an external library
aerowolf> which can provide DES services (libdes), that should be used
aerowolf> to help reduce the amount of cruft in the codebase.
Do you know that before we did the API change, crypto/des was libdes?
The trouble was that the variants of libdes that were floating around
were configured differently from the crypto/des variants, which caused
all kinds of clashes when some projects tried to be compatible with
both libdes and libcrypto...
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
Richard Levitte email@example.com
"When I became a man I put away childish things, including
the fear of childishness and the desire to be very grown up."
-- C.S. Lewis
OpenSSL Project http://www.openssl.org
Development Mailing List firstname.lastname@example.org
Automated List Manager email@example.com