On Sat, 26 Jun 1999, Jason wrote:
> Hi I am currently working on the SSLEAY crypto libraries and the Gemplus
> GPK4000 cards. When I sign a message using SSLEAY md5() and
> rsa_public_encrypt(), I get a signature string. However when I perform
> the signature using GPK4000 I get a different string. Both return 64
> bytes.
First of all, please don't use SSLeay anymore, as the project has been
renamed to OpenSSL (www.openssl.org). Eric Young is now working for RSA,
and SSLeay is no longer maintained.
Then... Are you sure the padding method used by the GPK4k is the same as
the one used by SSLeay?
> The keys which are loaded into the card were created by SSLEAY
> rsageneratekey(). These keys are then stored into file in ASCII format
> (0-F).These keys are then converted into a binary string and loaded into
> the card.
Are you sure the key components are correct for the GPK4k (this card has
some constraints for the key parameters).
> BTW. The plain text message before digest is 6 bytes (012345). I assume
> padding is done automatically by the SSLeay MD5 functions.
> RSAprivatencrypt uses PCKS-1 padding.
BTW: which version of SSLeay do you use?
--
Erwann ABALEA
System and Development Engineer - Certplus SA
[EMAIL PROTECTED]
- RSA PGP Key ID: 0x2D0EABD5 -
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
