Ludovic,
Please find the output you requested below.
systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2022-09-15 10:58:12 PDT; 1min 26s ago
Triggers: ● pcscd.service
Listen: /run/pcscd/pcscd.comm (Stream)
CGroup: /system.slice/pcscd.socket
systemctl status pcscd.service
● pcscd.service - PC/SC Smart Card Daemon
Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor
preset: enabled)
Active: active (running) since Thu 2022-09-15 10:58:16 PDT; 1min 31s ago
TriggeredBy: ● pcscd.socket
Docs: man:pcscd(8)
Main PID: 2544 (pcscd)
Tasks: 7 (limit: 38174)
Memory: 1.5M
CPU: 73ms
CGroup: /system.slice/pcscd.service
└─2544 /usr/sbin/pcscd --foreground --auto-exit
Let me provide additional information on the behavior that we are seeing
If we use
sudo systemctl enable pcscd.socket
then we must issue either
sudo systemctl restart pcscd.socket
sudo systemctl stop pcscd.socket; sudo systemctl start pcscd.socket
almost every time we want to use smartcard authentication at gnome login
screen
We have observed this behavior after the following events:
reboot
lock screen (seems to respond better to a stop and start of the socket rather
than a restart, e.g. we can get multiple locks where we are able to log back
in, if we stop and start the socket, whereas a restart just lets us get logged
back in once)
log out
output from /var/log/auth.log
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received
for user test.user: 7 (Authentication failure)
Sep 15 11:29:10 test-jammy gdm-password]: pam_pkcs11(gdm-password:auth): no
suitable token available
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth):
authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost=
user=test.user
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received
for user test.user: 7 (Authentication failure)
Sep 15 11:29:19 test-jammy gdm-smartcard]: pam_sss(gdm-smartcard:auth): User
info message: Please insert smart card
Commandline tools on the other hand seem to work as expected once the socket
has been enabled, no additional socket restarts are needed
opensc-tool --list-readers
pkcs11-tool --list-token-slots
pkcs11_listcerts debug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
pcscd 1.9.5-3 do not start automatically, only manual
Status in pcsc-lite package in Ubuntu:
Confirmed
Bug description:
Ubuntu Mate 22.04 with the latest updates.
Problem is present with internal smart-card reader and also external usb
smart-card reader.
eid-viewer sees no card reader,but When i do:
sudo pcscd -f
it is working, also following the tips of Ludovic:
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html
sudo systemctl stop pcscd.socket
sudo systemctl start pcscd.socket
It is working until next restart.
libacsccid1 version: 1.1.8-1
libccid version: 1.5.0-2
pcscd version: 1.9.5-3
eid-archive version: 2022.3
eid-mw version: 5.0.28v5.0.28-0u2204-1
eid-viewer version: 5.0.28v5.0.28-0u2204-1
In Firefox, my eid card is then also recognized, but only in the ESR
version, but this is a know Mozilla bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
