RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2070950 - Yubikey 4/5 not working after libusbx update
Summary: Yubikey 4/5 not working after libusbx update
Keywords:
Status: CLOSED DUPLICATE of bug 2058730
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libusbx
Version: CentOS Stream
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Benjamin Berg
QA Contact: Kernel-QE - Hardware
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-01 12:02 UTC by Daniel Uvehag
Modified: 2022-04-01 12:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-01 12:38:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-117626 0 None None None 2022-04-01 12:13:12 UTC

Description Daniel Uvehag 2022-04-01 12:02:33 UTC
Description of problem:

After installing CentOS Stream 9 20220302.0 and updating all packages, pcscd is no longer able to detect Yubikey security keys. My initial findings seem to point out libusbx to be the cause of this. Downgrading from libusbx-1.0.25-2.el9.x86_64 to libusbx-1.0.24-4.el9.x86_64 makes pcscd able to detect the Yubikey again.

Version-Release number of selected component (if applicable):

libusbx-1.0.25-2.el9.x86_64

How reproducible:

Every time. This has been tested on two different physical computers.

Steps to Reproduce:
1. Install CentOS Stream 9 20220302.0 with Smart Card Support.
2. Update the installation using dnf update.
3. Insert a Yubikey.
4. Check the status of pcscd.

Actual results:

# systemctl status pcscd.service
...
Apr 01 11:39:07 testmachine pcscd[2366]: 00000000 ccid_usb.c:863:WriteUSB() write failed (1/6): -4 LIBUSB_ERROR_NO_DEVICE

# p11tool --list-tokens
(Expected token not shown)

Expected results:
# systemctl status pcscd.service
(No errors)

# p11tool --list-tokens
...
Token 2:
	URL: pkcs11:model=PKCS%2315%20emulated;manufacturer=piv_II;serial=<REDACTED>;token=John%20Doe
	Label: John Doe
	Type: Hardware token
	Flags: RNG, Requires login
	Manufacturer: piv_II
	Model: PKCS#15 emulated
	Serial: <REDACTED>
	Module: opensc-pkcs11.so


Additional info:

Downgrading libusbx back to 1.0.24-4 makes the Yubikey available again.

Comment 1 Daniel Uvehag 2022-04-01 12:04:50 UTC
I tested this on Red Hat Enterprise Linux 9.0 Beta as well, and the same issue appears there.

This was all tested on physical hardware (one laptop, and two desktops).

Comment 2 Benjamin Berg 2022-04-01 12:38:25 UTC

*** This bug has been marked as a duplicate of bug 2058730 ***


Note You need to log in before you can comment on or make changes to this bug.