On Thu, Mar 21, 2002 at 02:45:18PM -0500, Jeffrey Altman wrote: >>> I prefer that des_old.h be compatible with libdes since that apps that >>> are built using it assume that the api they were using was constant >>> and unchanging.
>> The way things work now, there is at least no clash with libdes on the >> symbol level. >> >> The whole situation is otherwise a lose-lose one. There will always >> be someone loseing from the changes we make. Either we lose libdes >> compatibility by default or we lose the openssl 0.9.6 one. Take your >> pick. It has been pointed out (and I think I agree) that OpenSSL >> should prefer to be as compatible with the previous version of itself >> before being compatible with anything external (like libdes). > Yes, but let's remember the reason this whole situation came up in the > first place. There are a large number of applications that link to > both Kerberos 4 and OpenSSL in place of libdes.a. These applications > are not likely to be updated nor supported and yet we don't want to > see all of them break simply because they load des.h. Adding '-DOPENSSL_DES_LIBDES_COMPATIBILITY' to the compiler switches when compiling such applications should do the job. This is about as easy to do as linking with OpenSSL. -- Bodo Möller <[EMAIL PROTECTED]> PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html * TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt * Tel. +49-6151-16-6628, Fax +49-6151-16-6036 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
