I'm not using OpenSSL for the signing only for the verification on the server. On the client (MS workstation) I am currently using PKCS#11 DLLs/drivers supplied by the relevant vendors.
 
It's the OpenSSL (0.9.6) verification that is failing for this card.
 
regards
bruce
----- Original Message -----
From: Hotmail
Sent: Saturday, November 09, 2002 12:22 AM
Subject: Re: PKCS#11 and the Schlumberger smartcard

I'would be interested in how you can generate oncard keypairs and sign data for authentication with openssl, that is
the operating system you use (e.g. Linux Suse ..) , the openssl version (e.g. 0.9.6 -engine...). and eventually the command (e.g. openssl rsa ...), the driver (e.g. Muscle?).
I' ve a Gemplus card (GPK8000).
 
Thank you in advance.
 
Best regards.
Paolo
 
 
----- Original Message -----
Sent: Thursday, November 07, 2002 11:27 AM
Subject: PKCS#11 and the Schlumberger smartcard

I am using PKCS#11 libraries supplied by vendors (although I'm starting to look at openCryptoki) to generate oncard keypairs and sign data for authentication (non cert based).
 
However, when I then run the resulting signature through OpenSSL 0.9.6 RSA_public_decrypt() with padding type of RSA_PKCS1_PADDING we receive an error telling us that the padding type is incorrect (not block type 01). I have tried the other types.
 
This function works fine for GemSafe and AET cards.
 
Is anyone aware of a compatibility issue with the SB cards, a solution or what I may be doing wrong?
 
Any assistance much appreciated.
 
regards
bruce

Reply via email to