#354482 scdaemon: no timeout when connecting to pcscd

Package:
scdaemon
Source:
gnupg2
Description:
GNU privacy guard - smart card support
Submitter:
Simon Richter
Date:
2015-01-04 23:51:04 UTC
Severity:
important
#354482#5
Date:
2006-02-26 17:06:40 UTC
From:
To:
Hi,

if the smartcard daemon hangs, poldi waits forever for a connection to the
daemon, so it becomes impossible to logon or become superuser until the daemon
happens to become responsive again or dies.

It would be a good thing to set a (pretty small, about 10 seconds) timeout for
the connection, so the system can fall back in case the smartcard
authentication does not work.

   Simon

- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=de_DE.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages libpam-poldi depends on:
ii  libc6                         2.3.6-2    GNU C Library: Shared libraries an
ii  libgcrypt11                   1.2.2-1    LGPL Crypto library - runtime libr
ii  libgpg-error0                 1.1-4      library for common error values an
ii  libusb-0.1-4                  2:0.1.11-4 userspace USB programming library

Versions of packages libpam-poldi recommends:
ii  gnupg                         1.4.2-2    GNU privacy guard - a free PGP rep

- -- no debconf information
#354482#12
Date:
2006-03-31 19:34:48 UTC
From:
To:
What smartcard daemon are you referring to?  "scdaemon" doesn't make
sense in this context, as Poldi cannot make use of a running scdaemon.

Thanks,
Moritz
#354482#17
Date:
2006-04-01 13:12:07 UTC
From:
To:
Hi,

Moritz Schulte schrieb:

pcscd. That thing has several portability issues causing it to hang and
crash on bigendian and 64 bit architectures.

   Simon
#354482#22
Date:
2006-06-16 14:11:29 UTC
From:
To:
severity important
thanks

Hi,

after some thought, I'm downgrading the severity of this bug. It sure
can break your loginability, but so can any pam module if installed
incorrectly. In this case I think we can expect that the admin tests it
first (e.g. staying logged in, testing only for su).

But this bug will stay open until poldi is reportedly more robust.

I hope everyone agrees.

Greetings,
Joachim
#354482#29
Date:
2009-03-19 18:03:10 UTC
From:
To:
Hi,

I guess that even this bug should be moved to SCDaemon, for the reason
that Poldi (0.4) does not talk to pcscd directly. SCDaemon does.

thanks,
mo