Summary: | Cherry card reader doesn't work after upgrade to sys-apps/pcsc-lite-1.6.6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Gollowitzer <gollo> |
Component: | Current packages | Assignee: | Mikle Kolyada (RETIRED) <zlogene> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | amd64, sam |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Gollowitzer
2011-01-11 17:58:12 UTC
See, if it's not the same problem as in bug 349431. If so, same resolution for this bug. No, ccid was installed at any time. I reinstalled it now, but nothing has changed (despite that, GnuPG also has a CCID driver IIRC). I also installed pcsc-tools now and ran pcsc_scan, which didn't recognize any reader at all. Can you please try with the ccid-1.4.1-r2 package? There has been a few readers dropped in ccid-1.4.1 and they are restored in ~arch only for now as they required extensive upstream patching. It works with gpg now, but only if pcscd is started with the --auto-exit option. If pcscd is started via its init script, I'm getting the same error as before. I think this is *really* strange, so I will try a few other things in the next days. Thank you! Not sure if I should file a new bug yet, but the pcsc/ccid upgrade seems to have broken my CAC reader asetup (just a normal DoD CAC with the coolkey firefox module). It works with all previous versions prior to the recent upgrades (ie, it still works on my older install from last December). However, the current versions of pcsc and ccid stop coolkey from talking to the CAC (and makes firefox stop responding). Although pcsc_scan seems to see the reader and card the same as before, the green light on the card now goes out several seconds after plugging the card in, and doesn't come on again until firefox tries to talk to the card via coolkey (whereas on the working setup the green light stays on the whole time the card is plugged in). I'm still debugging this one, but everything so far points to pcsc_lite and/or ccid. That said, the upstream RedHat guys actually admitted they should release a new version of coolkey, so that *might* help. Non-working system: [ebuild R ] sys-apps/pcsc-lite-1.6.6 USE="usb" 0 kB [ebuild R ] dev-perl/pcsc-perl-1.4.11 0 kB [ebuild R ] app-crypt/ccid-1.4.1-r2 USE="usb -twinserial" 0 kB [ebuild R ] sys-apps/pcsc-tools-1.4.17 USE="gtk" 0 kB Working system: [ebuild U ] sys-apps/pcsc-lite-1.6.6 [1.6.4] USE="usb (-hal%) (-static%)" 0 kB [ebuild U ] dev-perl/pcsc-perl-1.4.11 [1.4.10] 0 kB [ebuild U ] app-crypt/ccid-1.4.1-r2 [1.4.0] USE="usb -twinserial" 0 kB [blocks b ] <app-crypt/ccid-1.4.1-r1 ("<app-crypt/ccid-1.4.1-r1" is blocking sys-apps/pcsc-lite-1.6.6) [ebuild R ] sys-apps/pcsc-tools-1.4.17 USE="gtk" 0 kB * Note: one of the recent workarounds (for a different issue) discussed on the coolkey list was to remove the CAC-1 patch from the set of upstream patches. Been there, tried that, didn't change anything on either system for me... The USB card reader is a generic one that works fine (when the software is working) on amd64 and ppc, and even with debian/ubuntu. The output below is the same on both the working and non-working installs: $ pcsc_scan PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr> Compiled with PC/SC lite version: 1.6.6 Scanning present readers... 0: Axalto Reflex USB v3 (21120538114863) 00 00 Wed Feb 16 16:59:41 2011 Reader 0: Axalto Reflex USB v3 (21120538114863) 00 00 Card state: Card inserted, ATR: 3B 7D 96 00 00 80 31 80 65 B0 83 11 17 D6 83 00 90 00 ATR: 3B 7D 96 00 00 80 31 80 65 B0 83 11 17 D6 83 00 90 00 + TS = 3B --> Direct Convention + T0 = 7D, Y(1): 0111, K: 13 (historical bytes) TA(1) = 96 --> Fi=512, Di=32, 16 cycles/ETU 250000 bits/s at 4 MHz, fMax for Fi = 5 MHz => 312500 bits/s TB(1) = 00 --> VPP is not electrically connected TC(1) = 00 --> Extra guard time: 0 + Historical bytes: 80 31 80 65 B0 83 11 17 D6 83 00 90 00 Category indicator byte: 80 (compact TLV data object) Tag: 3, len: 1 (card service data byte) Card service data byte: 80 - Application selection: by full DF name - EF.DIR and EF.ATR access services: by GET RECORD(s) command - Card with MF Tag: 6, len: 5 (pre-issuing data) Data: B0 83 11 17 D6 Tag: 8, len: 3 (status indicator) LCS (life card cycle): 00 (No information given) SW: 9000 (Normal processing.) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B 7D 96 00 00 80 31 80 65 B0 83 11 17 D6 83 00 90 00 DoD CAC card issued Jan 14, 2010 Please reopen if comment#7 is not helpful. Thanks. In systemd : systemctl start pcscd systemctl status pcscd ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: disabled) Active: active (running) since Mon 2021-10-11 18:37:37 CEST; 6s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 789487 (pcscd) Tasks: 5 (limit: 38372) Memory: 3.3M CPU: 9ms CGroup: /system.slice/pcscd.service └─789487 /usr/sbin/pcscd --foreground --auto-exit POERYZEN /usr/bin # pcsc_scan Using reader plug'n play mechanism Scanning present readers... 0: Cherry GmbH SmartTerminal XX44 00 00 Mon Oct 11 18:39:02 2021 Reader 0: Cherry GmbH SmartTerminal XX44 00 00 Event number: 0 Card state: Card inserted, ATR: 3B 98 XX 40 0A A5 03 01 01 01 AD XX XX ATR: 3B 98 XX 40 0A A5 03 01 01 01 AD XX XX + TS = 3B --> Direct Convention + T0 = 98, Y(1): 1001, K: 8 (historical bytes) TA(1) = 13 --> Fi=372, Di=4, 93 cycles/ETU 43010 bits/s at 4 MHz, fMax for Fi = 5 MHz => 53763 bits/s TD(1) = 40 --> Y(i+1) = 0100, Protocol T = 0 ----- TC(2) = 0A --> Work waiting time: 960 x 10 x (Fi/F) + Historical bytes: A5 03 01 01 01 AD XX XX Category indicator byte: A5 (proprietary format) Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): XX 98 XX 40 0A A5 03 01 01 01 AD XX XX After starting this service (for Openrc see also service :/etc/init.d/pcscd start) it works if everything is installed. It seems someone forgot to install the services in both systems. looks too old to reproduce It is still in use in Belgium an the European countries. So it is not obsolete. Still fabricated in keyboards and stand alone. So FIX it. It worked before in previous versions without a problem. So find the change in this version and the older versions. |