> Since this is about OpenSSL 0.9.4, it's obvious that page isn't quite > up-to-date. Since 0.9.6, OpenSSL comes in an engine variant that > contains support for several hardware crypto devices, among others > Rainbow CryptoSwift (which I test a little now and then, since I have > one of those). > > In other words, if you download openssl-engine-0.9.6c.tar.gz, you > should have support for your card in-the-box. It can be tested, for > example with the command 'openssl speed -engine cswift'. Please do > try it out, and come back if you get problems. > > Also, we've extended the engine framework in the current development > (which will eventually become 0.9.7), among others supporting > dynamically loadable engines. When and if Sun discovers that, they > will be able to support OpenSSL much more easily (if they wish to do > so).
Great. Glad to hear OpenSSL has been updated to accommodate these devices. Another question that I have after reading a cached copy of http://www.james.rcpt.to/2001/sun-crypto/ on google, I learned that these crypto cards only handle the Public key side of the SSL connection to Apache clients. Considering this, how can I estimate the load that would be saved by being able to offload PRNGD and the computationally expensive public key negotiation to the crypto card? Thanks in advance for your responses. Chris ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
