In message <[EMAIL PROTECTED]> on Fri, 11 Oct 2002 12:07:31 +0200,
Massimiliano Pala <[EMAIL PROTECTED]> said:
madwolf> Well, I am not sure about the PKCS#11 because I have not worked on it
madwolf> yet. I guess that if you code an engin that uses a PKCS#11 interface
madwolf> any PKCS#11 library you link (or dinamically load) will work with that
madwolf> ENGINE implementation.
The thing is that there's not really any preparation for PKCS#11 as it
is right now, and it seems like different vendors have named their
PKCS#11 libraries differently, and then make an engine that binds
specifically to that library...
madwolf> Another possibility would be to implement the ENGINE directly on top
madwolf> of the MuscleCard API and then you could code a PKCS#11 module using
madwolf> OpenSSL call with generic engine support.
I would suggest, to make it easier, that you go for the MuscleCard API
for now. There will be a generic PKCS#11 engine at some point, and
that should then be possible to use as well.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
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]
