Your message dated Wed, 23 Jun 2021 14:13:04 +0200
with message-id <[email protected]>
and subject line Re: Bug#925312: pcscd: Does not work if "used" in wrong order
has caused the Debian Bug report #925312,
regarding pcscd: Does not work if "used" in wrong order
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
925312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925312
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pcscd
Version: 1.8.24-1
Severity: important
Dear Maintainer,
I know the titel is confusing, so here:
I have a yubikey that got a gpg key on it. Worked perfectly fine in
stretch. Now it does not work half the time.
Thing is: If I plug the yubikey *BEFORE* anything that tries to get data
from it - it works perfectly.
If I do NOT plug the yubikey and start such an action (gpg sign for
example) - it does NOT work until I issue a sudo /etc/init.d/pcscd
restart.
So using a gpg decryption example: If I insert the yubikey first, then
start a gpg decryption, a dialog box opens for me to enter the pin. I
do, press enter, then press yubikey, all fine.
If I do NOT insert the yubikey and start the gpg decryption, a dialog
box with ok/cancel buttons opens saying "Please insert card XXXX YYYY".
I can insert the yubikey and press OK, it doesnt care, it asks again.
And continues asking until I cancel *OR* sudo restart pcscd. After the
sudo restart it happily talks to the yubikey and lets me enter pin,
press yubikey and done.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pcscd depends on:
ii libc6 2.28-7
ii libccid [pcsc-ifd-handler] 1.4.30-1
ii libpcsclite1 1.8.24-1
ii libsystemd0 241-1
ii libudev1 241-1
ii lsb-base 10.2018112800
pcscd recommends no packages.
Versions of packages pcscd suggests:
ii systemd 241-1
-- no debconf information
--
bye, Joerg
--- End Message ---
--- Begin Message ---
On Wed, 26 Jun 2019 11:43:11 +0200 Ludovic Rousseau <[email protected]>
wrote:
Hello Joerg,
I have no news from you since 3 months now.
I documented the problem and solution at
https://ludovicrousseau.blogspot.com/2019/06/gnupg-and-pcsc-conflicts.html
With no news from you I will consider that the problem is fixed with my
solution and close this Debian bug.
Closing now.
--
Dr. Ludovic Rousseau
--- End Message ---
