> From: Jeffrey Altman <[EMAIL PROTECTED]> > > jaltman> The only way that this can be handled is to use macros to map from > jaltman> the old api to the new functions. I do not see any other way that > jaltman> will allow the libdes.a to be mixed with libcrypto.a. > > I'm thinking you're right. At the same time, I want to retain C type > security as well as possible. How about this: I could rename all the > old functions to _old_des_* and then have cpp macros that map des_* to > _old_des_*. That would probably resolve all the issues.
Look at what we do in in kssl.c for mapping the kerberos functions from krb5_ to kssl_krb5_ in the windows world. That is exactly what you want to do in this case. Rename the real functions in the library. Then in the des.h header if USE_OLD_DES is defined you #define des_foo old_des_foo and expose the prototypes for the old_des_foo function. 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]
