From: Dr S N Henson <[EMAIL PROTECTED]>
drh> Then PEM_*_PrivateKey() should be able to handle it largely
drh> transparently and applications should be able to use the keys
drh> even if they aren't ENGINE aware.
Uhmmm, applications that use ENGINE will have to be ENGINE aware
enough to "load" the engine in question, otherwise, only the internal
ENGINE (our own software) is active, and that's that :-). Therefore,
if the application isn't ENGINE aware enough to at least load the
engine correctly will also not be able to use the kind of PEM file
that would refer to an engine or the indicated private key.
Or are you suggesting that the engine in question be loaded on the fly
whenever such a PEM file is encountered?
--
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]
