Bug 1226042 - yubikey 5 needs to disable CCID support again in 15.6
Summary: yubikey 5 needs to disable CCID support again in 15.6
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Pedro Monreal Gonzalez
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-06 12:29 UTC by Marcus Rückert
Modified: 2024-06-07 09:55 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Rückert 2024-06-06 12:29:37 UTC 
Rudi was just debugging a weird issue with yubikey 5 in 15.6 - during the search we found this https://github.com/void-linux/void-packages/issues/38034  which inturn references the nix package and that references this udev rules file https://salsa.debian.org/debian/gnupg2/-/blob/debian/unstable/debian/scdaemon.udev?ref_type=heads - should we maybe include this in our package as well? the current workaround seems otherwise to be to disable ccid in the scdaemon configuration.
Comment 1 Ruediger Oertel 2024-06-07 09:14:57 UTC 
update from 15.5 to 15.6 updates gpg2 from 2.2 to 2.4 and in

man scdaemon

you can find

       --disable-ccid
              The  integrated  CCID driver for CCID compliant devices can be available when libusb was detected at build time, and it is used to ac-
              cess the smartcard reader.  If access via PC/SC driver is needed, please configure this option to  disable  CCID  driver  support  (if
              any).  In GnuPG 2.2, there was a fallback mechanism from CCID driver to PC/SC driver.  The fallback mechanism worked, because scdaemon
              in GnuPG 2.2 only supported a single token/reader.  To support of multiple tokens/readers at the same time, fallback mechanism was re-
              moved.

and as I was relying on the fallback, things broke now.
Comment 2 Marcus Rückert 2024-06-07 09:55:11 UTC 
this might be worth mentioning in the releasenotes.