From: Jim Russell <[EMAIL PROTECTED]>
jrussell> I'd like to make an alternate suggestion -- that you instead
jrussell> *replace* the RSAref glue code with the BSAFE glue code
jrussell> (either the LymeWare or Bixby patches). There are still
jrussell> valid reasons for using the BSAFE API with OpenSsl. (One
jrussell> example would be interfacing with an IBM S/390 mainframe's
jrussell> hardware crypto, which exposes a BSAFE API.)
When you say "hardware crypto", my brain goes *dingdingdingdingding*!
The thing is that with the current snapshots, it would be perfectly
possible to create a BSAFE engine. That can be created completely
separately and be "grafted" into OpenSSL with ease. No more need for
patches.
That is one more reason not to have any more "glue" code in OpenSSL,
there are cleaner ways...
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.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]
