SCM SPR-332 pinpad

[Werner Koch]

On Wed, 20 Dec 2006 17:38, hawke at hawkesnest.net said:

> 2006-12-20 10:21:48 scdaemon[7324] DBG: ccid-driver: sending escape
> sequence to switch to a case 1 APDU
> 2006-12-20 10:21:48 scdaemon[7324] DBG: ccid-driver: sending 6B 03 00 00
> 00 00 11 00 00 00 80 02 00
> 2006-12-20 10:21:48 scdaemon[7324] DBG: ccid-driver: status: 00  error:
> 00  octet[9]: 00
>                data:

Sucessfully sent the escape sequence required fro SCM readers.

> 2006-12-20 10:21:48 scdaemon[7324] DBG: ccid-driver: sending 69 13 00 00
> 00 00 1
> 2 00 00 00 00 00 82 00 00 19 06 02 FF 04 09 00 00 40 00 00 20 00 82

Here we are sending the verify APDU template (00 20 00 82) to the
reader along with additional data to tell it how the reader should
append the PIN to the APDU.

> ---Here it asked for the PIN.  After entering the PIN and hitting enter:---

As expected.

> 2006-12-20 10:21:54 scdaemon[7324] DBG: ccid-driver: status: 00  error:
> 00  octe
> t[9]: 00
>                data: 00 40 02 90 00 D2

No error from reader and the card returned success (90 00).  Thus it
is verified and the PIN worked.

> 2006-12-20 10:21:54 scdaemon[7324] DBG: dismiss keypad entry prompt
> scdaemon[7324.0] DBG: -> INQUIRE DISMISSKEYPADPROMPT
> scdaemon[7324.0] DBG: <- END

This is to dismiss the popup window.

> Full log available at http://web.hawkesnest.net/users/hawke/scd.log

Well this log also ends here.  What you should see next is the usual
sign command.

So where is the problem?  Alright, I see: You tried to sign with the
card.  This has not been implemented yet.  I forgot about this because
I tested only the authntication as this is what I am using most of the
time (for ssh).  Nte that decryption should also work as ist uses the
CHV2 too.

I'll add code tomorrow to make signing work.


Salam-Shalom,

   Werner