AW: scdaemon lockup with Yubikey NEO

[the2nd]

Hi Ben,

We have a similar Problem since we've upgraded from Ubuntu 15.04 to 15.10.  When starting gpg-agent with --log-file the log show the following:

2015-05-30 13:49:36 gpg-agent[3600] error accessing card: Conflicting use
2015-05-30 13:49:36 gpg-agent[3600] smartcard signing failed: 
Conflicting use 
2015-05-30 13:49:38 gpg-agent[3600] error getting default authentication keyID of card: Conflicting use

I've asked the list serval times about this issue but got now answer yet. So i dont have a solution but it may be interesting if your problem is the same...

Regards
The2nd 

<div>-------- Ursprüngliche Nachricht --------</div><div>Von: Ben Warren <biggerbadderben at gmail.com> </div><div>Datum:11.20.2015  16:26  (GMT+01:00) </div><div>An: gnupg-users at gnupg.org </div><div>Betreff: scdaemon lockup with Yubikey NEO </div><div>
</div>Hi,

I’ve noticed several other problem reports that seem similar, hopefully they’re all related and there’s a simple fix.

The problem:

After an indeterminate amount of time (sometimes minutes, sometimes hours), any GPG operation that uses my Yubikey NEO device hangs.  The two most common operations are SSH authentication and git signing.  The following sequence gets things going again:

$ killall -SIGKILL scdaemon

$ gpg2 —card-status

System particulars:

Host OS is OS-X Yosemite, although it is also present on Mavericks (haven’t tried El Capitan yet)
GPG 2.1.5
Using the Yubikey’s authentication subkey to login to remote Linux hosts
Using the Yubikey’s signing subkey for git signing operations, both local and remote
Using gpg-agent for forwarding both GPG and SSH (great features, BTW!)


GPG configuration file:

$ cat ~/.gnupg/gpg-agent.conf

default-cache-ttl 1

ignore-cache-for-signing

no-allow-external-cache

max-cache-ttl 1

extra-socket ${HOME}/.gnupg/S.gpg-extra-agent

debug-all

log-file ${HOME}/.gnupg/mygpglogfile.log

enable-ssh-support



I’ll be happy to help debug this, but need some guidance.



thanks,

Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20151121/49e8aa05/attachment.html>