Pin fails with svn & ssh & gnupg-agent & smartcard.
wk at gnupg.org
Fri Jul 13 10:00:03 CEST 2007
On Thu, 12 Jul 2007 22:21, guillaume.yziquel at free.fr said:
> somehow to get in the same kind of problem that made me change from
> pcscd to scdaemon.
This is not related. scdaemon uses either its internal driver of pcscd.
If you are working _without gpg-agent_ than scdaemon does not come into
the game; gpg then uses either its internal driver or pcscd. The code
is more or less identical.
> Therefore, one small question: Should I use pcscd or scdaemon. What are
> the major pros and cons between these two solutions?
With the internal driver (i.e. without pcscd running) everything works.
pcscd has sometimes problem for long runnging operations like key
> And how does one usually attempt to localise the "bug" in this situation?
In a seperate xterms you may run
strace -p <pid-of-scdaemon> | less
to watch the interaction between scdaemon and the kernel.
More information about the Gnupg-users