Back to bug 2097048

Who When What Removed Added
Red Hat Bugzilla 2022-06-14 19:21:18 UTC Pool ID sst_desktop_rhel_8
Andrew Mike 2022-06-14 19:24:34 UTC CC alanm, brclark, casantos, jwright, mkielian, mkolbas, sbarcomb
Red Hat One Jira (issues.redhat.com) 2022-06-14 19:57:26 UTC Link ID Red Hat Issue Tracker RHELPLAN-125284
Steve Barcomb 2022-07-13 12:23:35 UTC Priority unspecified medium
Jakub Jelen 2022-08-31 08:11:47 UTC CC jjelen, rstrode
Flags needinfo?(rstrode)
Ray Strode [halfline] 2022-08-31 14:02:38 UTC Flags needinfo?(rstrode)
Steve Ross 2023-02-22 22:53:13 UTC CC sross
Marek Havrila 2023-02-27 12:27:26 UTC CC mhavrila
Jakub Jelen 2023-02-28 12:25:46 UTC QA Contact desktop-qa-list qe-baseos-security
Pool ID sst_desktop_rhel_8 sst_security_crypto_rhel_8
Status NEW ASSIGNED
Assignee rstrode jjelen
Component gdm opensc
Jakub Jelen 2023-02-28 14:06:22 UTC Keywords Triaged
Red Hat One Jira (issues.redhat.com) 2023-02-28 14:07:25 UTC Link ID Red Hat Issue Tracker CRYPTO-9631
Jakub Jelen 2023-03-02 09:28:23 UTC Target Release --- 8.9
Jakub Jelen 2023-03-02 17:53:23 UTC Doc Type If docs needed, set a value Known Issue
Doc Text Cause: When gdm is configured to lock screen on smartcard removal, the event is not triggered if the whole reader is removed.

Consequence: The computer might stay unlocked when it should be locked

Workaround (if any): Remove only smart card (if possible -- impossible with HW tokens which integrate both reader and "card). Or update to RHEL9.

Result: ?
Stanislav Zidek 2023-03-07 12:12:49 UTC QA Contact qe-baseos-security mhavrila
Lucie Vařáková 2023-03-08 13:51:15 UTC Docs Contact mjahoda
Mirek Jahoda 2023-03-29 13:10:53 UTC Flags needinfo?(jjelen)
Doc Text Cause: When gdm is configured to lock screen on smartcard removal, the event is not triggered if the whole reader is removed.

Consequence: The computer might stay unlocked when it should be locked

Workaround (if any): Remove only smart card (if possible -- impossible with HW tokens which integrate both reader and "card). Or update to RHEL9.

Result: ?
.The screen lock does not work when a smart-card reader is removed

The `opensc` packages incorrectly handle removing USB smart-card readers. Consequently, the system remains unlocked even when the GNOME Display Manager (GDM) is configured to lock the screen when a smart card is removed. Furthermore, after you reconnect the USB reader, the screen also does not lock after removing the smart card.

To work around this problem, perform one of the following actions:

* Always remove only a smart card, not a smart-card reader.
* When using hardware tokens that integrate a reader and a card in one package, upgrade to RHEL 9.
Jakub Jelen 2023-03-30 07:44:48 UTC Flags needinfo?(jjelen)
Mirek Jahoda 2023-04-06 13:43:57 UTC Doc Text .The screen lock does not work when a smart-card reader is removed

The `opensc` packages incorrectly handle removing USB smart-card readers. Consequently, the system remains unlocked even when the GNOME Display Manager (GDM) is configured to lock the screen when a smart card is removed. Furthermore, after you reconnect the USB reader, the screen also does not lock after removing the smart card.

To work around this problem, perform one of the following actions:

* Always remove only a smart card, not a smart-card reader.
* When using hardware tokens that integrate a reader and a card in one package, upgrade to RHEL 9.
.The automatic screen lock does not work when a smart-card reader is removed

The `opensc` packages incorrectly handle removing USB smart-card readers. Consequently, the system remains unlocked even when the GNOME Display Manager (GDM) is configured to lock the screen when a smart card is removed. Furthermore, after you reconnect the USB reader, the screen also does not lock after removing the smart card.

To work around this problem, perform one of the following actions:

* Always remove only a smart card, not a smart-card reader.
* When using hardware tokens that integrate a reader and a card in one package, upgrade to RHEL 9.
Jakub Jelen 2023-07-03 12:25:13 UTC Status ASSIGNED MODIFIED
errata-xmlrpc 2023-07-10 18:01:12 UTC Fixed In Version opensc-0.20.0-5.el8
Status MODIFIED ON_QA
George Pantelakis 2023-08-02 12:32:37 UTC Status ON_QA VERIFIED
CC gpantela
Jakub Jelen 2023-08-28 11:40:43 UTC Doc Text .The automatic screen lock does not work when a smart-card reader is removed

The `opensc` packages incorrectly handle removing USB smart-card readers. Consequently, the system remains unlocked even when the GNOME Display Manager (GDM) is configured to lock the screen when a smart card is removed. Furthermore, after you reconnect the USB reader, the screen also does not lock after removing the smart card.

To work around this problem, perform one of the following actions:

* Always remove only a smart card, not a smart-card reader.
* When using hardware tokens that integrate a reader and a card in one package, upgrade to RHEL 9.
.The automatic screen lock did not work when a smart-card reader is removed

The `opensc` packages incorrectly handled removing USB smart-card readers. Consequently, the system could remain unlocked even when the GNOME Display Manager (GDM) is configured to lock the screen when a smart card reader was removed.

This was fixed with the update to RHEL8 and screen should correctly lock even when the token or whole card reader are removed.
Doc Type Known Issue Bug Fix
Mirek Jahoda 2023-08-29 15:45:17 UTC Doc Text .The automatic screen lock did not work when a smart-card reader is removed

The `opensc` packages incorrectly handled removing USB smart-card readers. Consequently, the system could remain unlocked even when the GNOME Display Manager (GDM) is configured to lock the screen when a smart card reader was removed.

This was fixed with the update to RHEL8 and screen should correctly lock even when the token or whole card reader are removed.
.The automatic screen lock now works correctly even when a USB smart-card reader is removed

Before RHEL 8.9, the `opensc` packages incorrectly handled removing USB smart-card readers. Consequently, the system remained unlocked even if the GNOME Display Manager (GDM) was configured to lock the screen when a smart card was removed. Furthermore, after the USB reader was reconnected, the screen also did not lock after removing the smart card. In this release, the code for handling removals of USB smart-card readers has been fixed. As a result, the screen is correctly locked even when a smart card or a USB smart-card reader is removed.
Mirek Jahoda 2023-08-29 15:46:37 UTC Doc Text .The automatic screen lock now works correctly even when a USB smart-card reader is removed

Before RHEL 8.9, the `opensc` packages incorrectly handled removing USB smart-card readers. Consequently, the system remained unlocked even if the GNOME Display Manager (GDM) was configured to lock the screen when a smart card was removed. Furthermore, after the USB reader was reconnected, the screen also did not lock after removing the smart card. In this release, the code for handling removals of USB smart-card readers has been fixed. As a result, the screen is correctly locked even when a smart card or a USB smart-card reader is removed.
.The automatic screen lock now works correctly even when a USB smart-card reader is removed

Before RHEL 8.9, the `opensc` packages incorrectly handled removing USB smart-card readers. Consequently, the system remained unlocked even if the GNOME Display Manager (GDM) was configured to lock the screen when a smart card was removed. Furthermore, after reconnecting the USB reader, the screen also did not lock after removing the smart card. In this release, the code for handling removals of USB smart-card readers has been fixed. As a result, the screen is correctly locked even when a smart card or a USB smart-card reader is removed.

Back to bug 2097048