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.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-733-72 88 11
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, GemPlus: http://www.gemplus.com/
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]
