From: Jeffrey Altman <[EMAIL PROTECTED]> jaltman> I prefer that des_old.h be compatible with libdes since that apps that jaltman> are built using it assume that the api they were using was constant jaltman> 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). jaltman> The apps that were designed to use OpenSSL were warned many times that jaltman> the API set would change with each build. There are many other things jaltman> I need to change in my app to make it build with earlier versions of jaltman> OpenSSL. Adding an additional #define to that list is not a big jaltman> deal. That makes the decision even easier. Thanks. jaltman> > And oh, I wrote another blurb about DES_INT a while ago. jaltman> No reaction at all. I'd like a reaction, very much even... jaltman> jaltman> I must have missed this one. Please repost or send the archive link. http://marc.theaimsgroup.com/?t=101512079300001&r=1&w=2 -- Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ Unsolicited commercial email is subject to an archival fee of $400. See <http://www.stacken.kth.se/~levitte/mail/> for more info. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
