> So, if I would set des_old.h to have 0.9.6c compatibility, I would > remove the requirement to defined the macro > OPENSSL_DES_PRE_0_9_7_COMPATIBILITY, and instead require that one > defines OPENSSL_LIBDES_COMPATIBILITY if that's what one wants. > > Unfortunately, I have a hard time deciding, so I'm requesting your > help. I know that there are developers out there that have dealt with > all this before and discussed it with me, on this list and otherwise. > Please speak up and say what you think of all this.
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 apps that were designed to use OpenSSL were warned many times that the API set would change with each build. There are many other things I need to change in my app to make it build with earlier versions of OpenSSL. Adding an additional #define to that list is not a big deal. > And oh, I wrote another blurb about DES_INT a while ago. No reaction > at all. I'd like a reaction, very much even... I must have missed this one. Please repost or send the archive link. - Jeff Jeffrey Altman * Sr.Software Designer C-Kermit 8.0 available now!!! The Kermit Project @ Columbia University includes Telnet, FTP and HTTP http://www.kermit-project.org/ secured with Kerberos, SRP, and [EMAIL PROTECTED] OpenSSL. Interfaces with OpenSSH ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
