Summary: | =app-crypt/gnupg-2.1.18 scdaemon cannot access YubiKey or Lenovo Integrated SC Reader | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marek Szuba <marecki> |
Component: | Current packages | Assignee: | Kristian Fiskerstrand (RETIRED) <k_f> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | anton.bugs, sir.suriv |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.gnupg.org/gnupg/issue2933 | ||
See Also: | https://bugs.debian.org/854595 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 617960 | ||
Bug Blocks: | 611250 |
Description
Marek Szuba
2017-03-07 23:14:46 UTC
Try with disable-ccid in scdaemon.conf and install app-crypt/ccid (killing scdaemon to ensure new drivers are used) I see the same effect with the smart card reader in my Thinkpad T520, Bus 002 Device 004: ID 17ef:1003 Lenovo Integrated Smart Card Reader I have not tried k_f's advice yet, since I first went to the upstream bug. However, I can confirm that adding the two Debian patches from $URL to our 2.1.18 solves the problem for me, and I can access my card reader again. For the record, at least in case of YK4 disabling the built-in CCID driver in favour of the external one does help. (In reply to Marek Szuba from comment #3) > For the record, at least in case of YK4 disabling the built-in CCID driver > in favour of the external one does help. Also of interest is whether the issue persists in 2.1.19 Installing 2.1.19-r1 fixed the problem for me (YubiKey 4). The relevant bug report seems below: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852702 and the patch is here: https://anonscm.debian.org/cgit/pkg-gnupg/gnupg2.git/commit/?id=cd2ad84410ba2045338a30a15c1caa145335c445 (In reply to Diogo Pereira from comment #5) > Installing 2.1.19-r1 fixed the problem for me (YubiKey 4). Right, the mentioned patches are included in it so I'm not surprised. So if the workaround isn't sufficient I'd prefer stabilizing 2.1.19 rather than applying the specific patches. Already stable on all but ia64, so closing this bug |