-Original Message-
From: Viktor Tarasov [mailto:viktor.tara...@gmail.com]
Sent: Monday, August 15, 2011 10:34 PM
To: TMS Brokers / Łukasz Kościesza
Cc: Douglas E. Engert; opensc-devel@lists.opensc-project.org
Subject: Re: [opensc-devel] Cryptotech Setcos card signing problem
Hello,
Le
-Original Message-
From: Douglas E. Engert [mailto:deeng...@anl.gov]
Sent: Friday, August 12, 2011 4:55 PM
To: TMS Brokers / Łukasz Kościesza
Cc: opensc-devel@lists.opensc-project.org
Subject: Re: [opensc-devel] Cryptotech Setcos card signing problem
Developers,
Could this be a card
Hi all,
I'm trying to sign a file using compiled from sources opensc 12.2.
Card is manufactured by Cryptotech and it has setcos 4.1.1 on board.
The card was initialized by www.sigillum.plhttp://www.sigillum.pl company.
Even though PIN is fine and there are no failures in the card reading process
Setcos card signing problem
It looks like you did not logon to the card.
Did the program ever ask for the pin?
What program are you using?
On 8/12/2011 7:05 AM, TMS Brokers / Łukasz Kościesza wrote:
Hi all,
I’m trying to sign a file using compiled from sources opensc 12.2.
Card
OK, I'm attaching the log file:
And I was able to sniff USB communication with card reader with native windows
middleware for comparition:
01 A0 00 07 - 00 A4 08 00 02 DF 01
01 00 00 02 - 61 22
01 A0 00 05 - 00 C0 00 00 22
01 00 00 24 - (40 bytes - some id?)
01 A0 00 05 - 00 20 00 81 00
01 00 00
0xb7ad06c0 17:20:12.324 [opensc-pkcs11] card.c:330:sc_unlock: called
0xb7ad06c0 17:20:12.324 [opensc-pkcs11] card.c:330:sc_unlock: called
0xb7ad06c0 17:20:12.324 [opensc-pkcs11] iso7816.c:320:iso7816_process_fci:
processing FCI bytes
0xb7ad06c0 17:20:12.324 [opensc-pkcs11]
0xb7ad06c0 17:20:13.248 [opensc-pkcs11] apdu.c:184:sc_apdu_log:
Outgoing APDU data [5 bytes] =
00 B0 01 00 00 .
==
0xb7ad06c0 17:20:13.248 [opensc-pkcs11]
