poldi bug: SIGSEGV if no reader
mo at g10code.com
Sat Apr 1 11:33:58 CEST 2006
> Similarly, if another application (such as scdaemon) is holding the
> card open from pcscd, pcscd tells poldi "sharing violation" and poldi
> aborts the whole process rather than cleanly returning a PAM code for
> "couldn't authenticate".
Hmm.. I have scdaemon running right now. And trying to use Poldi causes
the authentication process to fail with the following messages in my
Mar 31 19:30:16 localhost su: [Poldi] pcsc_establish_context
failed: no service (0x8010001d)
Mar 31 19:30:17 localhost su: [Poldi] Failure: Card error
Mar 31 19:30:17 localhost su: pam_authenticate: Authentication
Mar 31 19:30:17 localhost su: - pts/6 moritz:root
I am not sure where exactly Poldi aborts execution for you.
> I understand scdaemon is holding the card open to allow PIN caching?
Not really. scdaemon is simply an smartcard access middleware for our
Gnupg components. It provides a high-level interface for smartcard
related operations like e.g. cryptographic operations, retrival of
smartcard data, etc.
> That's rather problematic, because then it will never be able to
> coexist peacefully with poldi.
Right now, scdaemon and poldi cannot run simultanously - sad but true.
Hopefuly this will be solved one day.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : /pipermail/attachments/20060401/5a0d557e/attachment.pgp
More information about the Gnupg-devel