On 13.12.2001 10:49:31 Richard Levitte - VMS Whacker wrote:
>Assuming you have reached a point where you have a RSA that contains >the public data in a form that OpenSSL understands, and a reference >(completely chosen by you) to the private data on the card in ex_data, >you can now do the following (assuming res is of the type EVP_PKEY *): > > res = EVP_PKEY_new(); > EVP_PKEY_assign_RSA(res, rsatmp); > >This is exactly how it's done in crypto/engine/hw_ncipher.c, why don't >you take a look at that file? Hi Richard, I had a look at that code, but I just don't like copying things without knowing what I'm doing ;-) What do you mean by "you have a RSA that contains the public data" ? I really don't understand why I need a EVP_PKEY with a pointer to a RSA struct. The DER encoded X.509 certificate is read from the card. I don't have and need access to the private key in the card, I only have to make sure the right key is used during the SSL handshake, but that's easy also without a dummy/proxy/shadow (whatever one could call it) EVP_PKEY. If I have to provide a EVP_PKEY (e.g. by ENGINE_load_private_key), with what information do I fill it? What data do I put into the RSA struct? (I don't have any private data and I guess my own public key is not used during the handshake. Besides, it's already in the certificate) I'm sorry I keep going on with this, but it's still not satisfying. Alex. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
