Hello Joerg,
I have no news from you since 3 months now.
I documented the problem and solution at
https://ludovicrousseau.blogspot.com/2019/06/gnupg-and-pcsc-conflicts.html
With no news from you I will consider that the problem is fixed with my
solution and close this Debian bug.
Regards,
Le 24/03/2019 à 22:15, Ludovic Rousseau a écrit :
Le 24/03/2019 à 22:05, Ludovic Rousseau a écrit :
Le 24/03/2019 à 21:19, Joerg Jaspert a écrit :
On 15351 March 1977, Ludovic Rousseau wrote:
I think I found the problem.
I think my system disagrees. :)
In my case "gpg --card-status" works only if pcscd is NOT running.
GnuPG has its own way to access the smart card readers (here a yubikey)
Its a yubikey here too.
I propose two possible solutions:
1. remove pcscd from your system but that is a drastic change. No
PC/SC application will work any more.
Not a good thing, it's there for a reason.
And I know it worked in stretch.
2. configure scdaemon to NOT use its internal CCID driver but use the PC/SC
interface instead
To make option 2 just edit/create the scdaemon configuration file as bellow:
$ cat ~/.gnupg/scdaemon.conf
disable-ccid
Done that. Doesn't do anything.
Logged out. Killed gpg agent (just in case). Rebooted (damn system,
maybe). Nope, nothing. Same behaviour as before.
:-(
Before you restart pcscd, can you see your YubiKey listed by the pcsc_scan
command (from the pcsc-tools package)?
Does "gpg --card-status" works as expected?
Once you have restarted pcscd, can you see your YubiKey listed by the pcsc_scan
command?
Does "gpg --card-status" works as expected?
What are the USB VendorID & ProductID of your YukiKey token?
You can just attach the output of lsusb.
Thanks
--
Dr. Ludovic Rousseau
