Hello,
On 23.10.2013 0:37, Martin Wolters wrote:
I am using gpg4win 2.2.1, which according to the change log supports
the SPR332 PIN-pad, but pinentry requests the PIN from the keyboard.
Is there anything I need to configure to enforce the entry from the
card reader?
I'm having the exact same problem in gpg4win 2.2.1 with SPR 532
(firmware 5.10), Windows 7 64-bit. In Linux the pinpad worked by default
just fine, no separate configuration needed. I have not done any special
configuration of gpg4win related to pinpad usage, but I have installed
the regular drivers provided by SCM. When I plug my openpgp v2 card into
the reader slot, Windows pops up a notification "Device driver software
was not successfully installed", but I'm assuming it's normal and due to
Windows itself not understanding openpgp cards?
Here are a few excerpts from my scdaemon log that might or might not be
relevant. This is from logging into an ssh server using putty and a key
stored in the authentication slot, pin input via pinentry/keyboard. If
you need something more verbose, let me know. (BTW it would be nice to
be able to export the ssh-compatible authorized_keys pubkey line
directly via some more integrated way, gpgkey2ssh isn't supplied in
gpg4win. Is there something similar?)
2013-10-23 23:43:05 scdaemon[792] listening on socket
`C:\Users\username\AppData\Roaming\gnupg\S.scdaemon'
2013-10-23 23:43:05 scdaemon[792] handler for fd -1 started
2013-10-23 23:43:05 scdaemon[792] detected reader `SCM Microsystems Inc.
SPRx32 USB Smart Card Reader 0'
2013-10-23 23:43:05 scdaemon[792] pcsc_control failed: invalid PC/SC
error code (0x6)
2013-10-23 23:43:05 scdaemon[792] pcsc_vendor_specific_init:
GET_FEATURE_REQUEST failed: 65547
2013-10-23 23:43:05 scdaemon[792] reader slot 0: not connected
2013-10-23 23:43:06 scdaemon[792] reader slot 0: active protocol: T1
2013-10-23 23:43:06 scdaemon[792] slot 0: ATR=3B DA 18 FF 81 B1 FE 75 1F
03 00 31 C5 73 C0 01 40 00 90 00 0C
2013-10-23 23:43:06 scdaemon[792] Historical Bytes: 00 31 C5 73 C0 01 40
05 90 00
2013-10-23 23:43:06 scdaemon[792] Version-2 ......: yes
2013-10-23 23:43:06 scdaemon[792] Get-Challenge ..: yes (2048 bytes max)
2013-10-23 23:43:06 scdaemon[792] Key-Import .....: yes
2013-10-23 23:43:06 scdaemon[792] Change-Force-PW1: yes
2013-10-23 23:43:06 scdaemon[792] Private-DOs ....: yes
2013-10-23 23:43:06 scdaemon[792] Algo-Attr-Change: yes
2013-10-23 23:43:06 scdaemon[792] SM-Support .....: no
2013-10-23 23:43:06 scdaemon[792] Max-Cert3-Len ..: 2048
2013-10-23 23:43:06 scdaemon[792] Max-Cmd-Data ...: 2048
2013-10-23 23:43:06 scdaemon[792] Max-Rsp-Data ...: 2048
2013-10-23 23:43:06 scdaemon[792] Cmd-Chaining ...: no
2013-10-23 23:43:06 scdaemon[792] Ext-Lc-Le ......: yes
2013-10-23 23:43:06 scdaemon[792] Status Indicator: 05
2013-10-23 23:43:06 scdaemon[792] GnuPG-No-Sync ..: no
2013-10-23 23:43:06 scdaemon[792] GnuPG-Def-PW2 ..: no
2013-10-23 23:43:06 scdaemon[792] Key-Attr-sign ..: RSA, n=4096, e=32,
fmt=std
2013-10-23 23:43:06 scdaemon[792] Key-Attr-encr ..: RSA, n=4096, e=32,
fmt=std
2013-10-23 23:43:06 scdaemon[792] Key-Attr-auth ..: RSA, n=4096, e=32,
fmt=std
2013-10-23 23:43:06 scdaemon[792] updating slot 0 status: 0x0000->0x0007
(0->1)
2013-10-23 23:43:06 scdaemon[792] triggering event 100 (00000100) for
client -1
2013-10-23 23:43:10 scdaemon[792] DBG: check_pcsc_pinpad: command=20,
r=27265
2013-10-23 23:43:10 scdaemon[792] DBG: asking for PIN '||Please enter
the PIN'
2013-10-23 23:43:21 scdaemon[792] operation auth result: Success
Tapio
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
