Looks like I forgot to add --sha-1 argument to pkcs15-crypt. Is it correct now? zapr-SHA-1 contains SHA-1 hash of some file.
% pkcs15-crypt -p 123456 -s --sha-1 -i zapr-SHA-1 --pkcs1 -o signed Patched: http://akson.sgh.waw.pl/~saper/opensc/pkcs15-sign-patched-debug-sha1.log Unpatched: http://akson.sgh.waw.pl/~saper/opensc/pkcs15-sign-unpatched-debug-sha1.log Now at least last "raw" operation is executed, although we get 0x6a81 anyway. 16 bit MD5 file with --md5 gives me also 0x6a81 error. % pkcs11-tool --slot 0 -M Supported mechanisms: SHA-1, digest MD5, digest RIPEMD160, digest RSA-X-509, sign, verify, unwrap, decrypt RSA-PKCS, sign, verify, unwrap, decrypt SHA1-RSA-PKCS, sign, verify MD5-RSA-PKCS, sign, verify RIPEMD160-RSA-PKCS, sign, verify RSA-PKCS-KEY-PAIR-GEN, keypairgen Both MD5 and SHA-1 hashing work fine using the pkcs11-tool. -- << Marcin Cieslak // [EMAIL PROTECTED] >>
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
