Re: Keypad support for PC/SC card readers?
Hello I trid it with gnupg 2.0.19-1 from debian testing - PIN is not requested from the card reader. here is the log file. I did use testing keys and non-productive PIN so I hope I did not post anything sensitive 2012-12-04 22:05:10 scdaemon[16008] listening on socket `/tmp/gpg-iJ5FQq/S.scdaemon' 2012-12-04 22:05:10 scdaemon[16008] handler for fd -1 started 2012-12-04 22:05:11 scdaemon[16008] reader slot 0: not connected 2012-12-04 22:05:11 scdaemon[16008] slot 0: ATR=3B DA 18 FF 81 B1 FE 75 1F 03 00 31 C5 73 C0 01 40 00 90 00 0C 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=A4 p1=00 p2=0C lc=2 le=-1 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 A4 00 0C 02 3F 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=6B00 datalen=0 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=A4 p1=04 p2=00 lc=6 le=-1 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 A4 04 00 06 D2 76 00 01 24 01 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=0 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=CA p1=00 p2=4F lc=-1 le=256 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 CA 00 4F 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=16 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: D2 76 00 01 24 01 02 00 00 05 00 00 12 98 00 00 2012-12-04 22:05:11 scdaemon[16008] AID: D2 76 00 01 24 01 02 00 00 05 00 00 12 98 00 00 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=CA p1=5F p2=52 lc=-1 le=256 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 CA 5F 52 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=10 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: 00 31 C5 73 C0 01 40 05 90 00 2012-12-04 22:05:11 scdaemon[16008] Historical Bytes: 00 31 C5 73 C0 01 40 05 90 00 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 CA 00 C4 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=7 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: 00 20 20 20 03 00 03 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 CA 00 6E 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=217 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: 4F 10 D2 76 00 01 24 01 02 00 00 05 00 00 12 98 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C BA F7 CF 1F 37 93 D7 CA 56 25 35 E9 45 3C F3 78 19 5B B1 40 06 90 84 2F E5 88 92 F0 B9 BC F7 61 D2 33 94 64 B6 0B 2A D6 EA 4C 60 4A 5B A6 50 C2 82 52 95 30 82 0A E5 BB 3D 0A 33 95 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 50 BE 63 F2 50 BE 63 F2 50 BE 63 F2 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=CA p1=00 p2=5E lc=-1 le=256 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 CA 00 5E 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=0 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: 2012-12-04 22:05:11 scdaemon[16008] Version-2 ..: yes 2012-12-04 22:05:11 scdaemon[16008] Get-Challenge ..: yes (2048 bytes max) 2012-12-04 22:05:11 scdaemon[16008] Key-Import .: yes 2012-12-04 22:05:11 scdaemon[16008] Change-Force-PW1: yes 2012-12-04 22:05:11 scdaemon[16008] Private-DOs : yes 2012-12-04 22:05:11 scdaemon[16008] Algo-Attr-Change: yes 2012-12-04 22:05:11 scdaemon[16008] SM-Support .: no 2012-12-04 22:05:11 scdaemon[16008] Max-Cert3-Len ..: 2048 2012-12-04 22:05:11 scdaemon[16008] Max-Cmd-Data ...: 2048 2012-12-04 22:05:11 scdaemon[16008] Max-Rsp-Data ...: 2048 2012-12-04 22:05:11 scdaemon[16008] Cmd-Chaining ...: no 2012-12-04 22:05:11 scdaemon[16008] Ext-Lc-Le ..: yes 2012-12-04 22:05:11 scdaemon[16008] Status Indicator: 05 2012-12-04 22:05:11 scdaemon[16008] GnuPG-No-Sync ..: no 2012-12-04 22:05:11 scdaemon[16008] GnuPG-Def-PW2 ..: no 2012-12-04 22:05:11 scdaemon[16008] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2012-12-04 22:05:11 scdaemon[16008] DBG: PCSC_data: 00 CA 00 6E 00 2012-12-04 22:05:11 scdaemon[16008] DBG: response: sw=9000 datalen=217 2012-12-04 22:05:11 scdaemon[16008] DBG: dump: 4F 10 D2 76 00 01 24 01 02 00 00 05 00 00 12 98 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C BA F7 CF 1F 37 93 D7 CA 56 25 35 E9 45 3C F3 78 19 5B B1 40 06 90 84 2F E5 88 92 F0 B9 BC F7 61 D2 33 94 64 B6 0B 2A
Re: Keypad support for PC/SC card readers?
On Sun, 2 Dec 2012 10:57, cry...@artemicode.de said: I suppose gnupg tries to detect whether a keypad is available. Is that logged? Which debugging level would be needed. 2.0.19 has support for keypads via PC/SC. Add this to ~/.gnupg/scdaemon.conf log-file /some/file debug 2048 Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Keypad support for PC/SC card readers?
Am 02.12.2012 01:19, schrieb Hauke Laging: Am Sa 01.12.2012, 22:47:17 schrieb Selene Feigl: This refers to regular card usage (signing and ecryptoing a file to myself and decrypting it afterwards). I was asked to enter the PIN for these operations on the text console for both operations. There is an option for scdaemon which prevents PIN pad usage: --disable-keypad Is that in the config file? There was no scdaemon.conf yet - so I suppose the answer is no. I suppose gnupg tries to detect whether a keypad is available. Is that logged? Which debugging level would be needed. Note: that is a PC/SC reader without CCID Selene Feigl ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Keypad support for PC/SC card readers?
Am 02.12.2012 21:09, schrieb Peter Lebbing: On 02/12/12 10:57, Selene Feigl wrote: Note: that is a PC/SC reader without CCID AFAIK, keypad entry is only supported through the internal CCID driver of GnuPG, not through a PC/SC stack. Peter. Ok that is sad, but it is an information at last. Is support planned or are there any technical restrictions that make it impossible Selene ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Keypad support for PC/SC card readers?
On 02/12/12 10:57, Selene Feigl wrote: Note: that is a PC/SC reader without CCID AFAIK, keypad entry is only supported through the internal CCID driver of GnuPG, not through a PC/SC stack. Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://digitalbrains.com/2012/openpgp-key-peter ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Keypad support for PC/SC card readers?
Hello, I have a PC/SC card reader (specifically a Reiner SCT cyberJack RFID komfort, which is an dual interface RFID/contact class 3 smart card reader (display/keypad) Out of the box the OpenPGP card is working, but the keypad of the card reader seems not to be used to enter the PIN. Is the keypad supposed to be working with gnupg 2.0.x with my reader? Is it possible to get it to work somehow? I offer to test patches if they are available. Although I am a developer, I have no idea of PC/SC / gnupg development. So I am probably not much help at the moment - that could change when someone points me to suitable information to get my keypad working. Greetings Selene Feigl ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Keypad support for PC/SC card readers?
Am Sa 01.12.2012, 17:40:04 schrieb Selene Feigl: Out of the box the OpenPGP card is working, but the keypad of the card reader seems not to be used to enter the PIN. Does this refer to setting / changing the PIN or to PIN entry for regular card usage? GnuPG does not support setting / changing the PIN via PIN pad. Whyever. Hauke -- ☺ PGP: 7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5 (seit 2012-11-04) signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Keypad support for PC/SC card readers?
Am Sa 01.12.2012, 22:47:17 schrieb Selene Feigl: This refers to regular card usage (signing and ecryptoing a file to myself and decrypting it afterwards). I was asked to enter the PIN for these operations on the text console for both operations. There is an option for scdaemon which prevents PIN pad usage: --disable-keypad Is that in the config file? Hauke -- ☺ PGP: 7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5 (seit 2012-11-04) signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
