On Mon 2017-02-06 19:55:58 -0500, Antoine Beaupré wrote: > the daemon stopped working again - even with disable-ccid: > > $ LANG=C gpg --card-status > gpg: selecting openpgp failed: No such device > gpg: OpenPGP card not available: No such device > > i got a different error now: > > fév 06 19:45:29 curie gpg-agent[1643]: gpg-agent (GnuPG) 2.1.18 starting in > supervised mode. > fév 06 19:45:29 curie gpg-agent[1643]: using fd 3 for std socket > (/run/user/1000/gnupg/S.gpg-agent) > fév 06 19:45:29 curie gpg-agent[1643]: using fd 4 for ssh socket > (/run/user/1000/gnupg/S.gpg-agent.ssh) > fév 06 19:45:29 curie gpg-agent[1643]: using fd 5 for extra socket > (/run/user/1000/gnupg/S.gpg-agent.extra) > fév 06 19:45:29 curie gpg-agent[1643]: using fd 6 for browser socket > (/run/user/1000/gnupg/S.gpg-agent.browser) > fév 06 19:45:29 curie gpg-agent[1643]: listening on: std=3 extra=5 browser=6 > ssh=4 > fév 06 19:45:29 curie gpg-agent[1643]: scdaemon[1645] pcsc_establish_context > failed: no service (0x8010001d) > > pcsc_establish_context failed: no service (0x8010001d) > > This is strange, because there hasn't been a change in the gpg software > since my last report, and I *thought* I had this fixed with the ccid > workaround. But it seems that doesn't work anymore. :( > > I have tried uninstalling pcscd, running the command again, same result. > > Now the oddest thing is - installing pcscd again fixed the problem. > > No idea what's going on here.
This sounds to me like pcscd crashed or otherwise terminated.
afaict, the two options are:
* pcsc
* ccid
the workaround i've seen mooted here of "disable-ccid" means that all
your eggs are in the pcsc basket. If pcscd fails or drops the card or
whatever, then scdaemon can't fall back to ccid.
did you have disable-ccid set in scdaemon.conf?
does this line of thinking make sense?
--dkg
signature.asc
Description: PGP signature
