Steve, Most of the time, applications call d2i/i2d public/private Key to load or store keys. load_private_key and load_public_key are not much used, and when used it still remains the problem to store keys in the hardware. Therefore it is mandatory to patch d2i/i2d functions to give to the PKCS#11 engine the ability of manage keys in the hardware. In 0.9.6 code, I could easily patch the code for these calls, and make it working with gpkcs11/ceay_token (software token) & pkcs11/cc2000_token (bull trustway hardware). But in 0.9.7 the entire code of the d2i/i2d functions is rewritten and the C-code is replaced by macros. Patching the new code isn't so obvious. So I am not sure about an efficient way to insert the engine calls in d2i/i2d functions and still remain non intrusive for other users (non-PKCS#11 engine callers).
Rather than asking now and again when I am going to submit a 0.9.7 pkcs#11 engine, I invite you to think about a solution and if you have a good proposal , share it please! afchine ______________________________________ [EMAIL PROTECTED] Bull - Trustway R&D - Networking & Security http://www.servers.bull.com/trustway > Steve Bade wrote: > Afchine > > When are you going to submit a 0.9.7 pkcs#11 engine?? > As I understand things, 0.9.6 will not have any new > submissions included.... 0.9.7 is probably frozen, but the > 0.9.8 function will be built on the 0.9.7 base and > a PKCS#11 engine for 0.9.7 would be more likely to be > incorporated into 0.9.8??? > > afchine madjlessi wrote: > > I've made some improvements in the Bull trustway pkcs#11 engine to be more generic. > > In this release, PKCS#11 functions are called through the functions list rather >than specific calls directly to PKCS#11 functions. So it is possible to point it to >any PKCS#11 shared library renamed libpkcs11.so on Linux. > > A new flag, RSA_FLAG_GEN_KEY is added to RSA_method to allow the use of the >additionnal entries (rsa_generate_key, i2d/d2i_RSAPrivate/PublicKey) for crypto cards >which can generate and store keys. > > PKCS#11 engine is added in crypto/engine/pkcs11. In the crypto code, rsagen & >d2i/i2dRSAPublic/PrivateKey functions can be redirected to the the PKCS11 engine when >RSA_FLAG_GEN_KEY is defined by the engine. > > This PKCS#11 engine identifier is "pkcs11" rather than trustway in the last >release. > > I've tested this engine with apache-mod_ssl & cc2000 Bull crypto card on Linux. It >have been tested also on Win32. > > Cheers, > > Afchine Madjlessi > > ______________________________________ > > [EMAIL PROTECTED] > > Bull - Trustway R&D - Networking & Security > > http://www.servers.bull.com/trustway > > > > > > > > ______________________________________________________________________ > > OpenSSL Project http://www.openssl.org > > Development Mailing List [EMAIL PROTECTED] > > Automated List Manager [EMAIL PROTECTED] > > > -- > > --- > Steven Bade > Senior Software Engineer > IBM Linux Technology Center > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > > Security > "this mess is so big and so bad and so tall, > we cannot clean it up, there is no way at all" > (Cat in the Hat) > > > "Two-way communication is necessary to proactively facilitate acceptance > and involvement and to get insights about the journey it takes to get > where we want" > > > Who cares about converting MPH to KPH. I want to convert to > Furlongs per Fortnight > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
