From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnupg-2.3: scdaemon disables PC/SC fallback if CCID is enabled, breaks smartcards
Date: Wed, 13 Jul 2022 07:04:40 +0200 [thread overview]
Message-ID: <20220713050440.UX3Xg0vrQ7VOSHVSgCGuw1as1hSBA8gQMbznMard6iE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38034@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/issues/38034#issuecomment-1182770242
Comment:
The problem is much worse than it seems at first. The internal CCID driver is not what's new; it's quite old and there's traces of it breaking pcscd all over the web from before gnupg 2.3 (`2021-04-07`). Here's some bug reports and blog posts from 2019;
- https://github.com/LudovicRousseau/PCSC/issues/65
- https://ludovicrousseau.blogspot.com/2019/06/gnupg-and-pcsc-conflicts.html
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925312
What's new is that gnupg 2.3 dropped the automatic fallback to pcscd when the internal driver fails (https://dev.gnupg.org/T4673). That fallback was what we all used since void and (most) distros never shipped any udev rules that would allow the built-in driver to work.
I think that option 1 would be fine, but would imo require at minimum a `README.void` file.
But it's unclear to me if option 3 is realistic at all, seeing how there's no official or otherwise recognised set of udev rules, and the Debian ones are so barebones that they don't even include any Yubico devices from after the Yubikey 4, like my Yubikey 5. We'd have to maintain a set of rules and that seems like a major task.
I'd say option 2 might be best.
Regarding my previous comment on plugdev/uaccess, it seems it might not be relevant since rules like the ones Debian ships appear to use a completely different permission mechanism that I don't quite comprehend. Maybe it's some weirder logind stuff that might not work here, or Debian-specific things.
next prev parent reply other threads:[~2022-07-13 5:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 23:53 [ISSUE] " lemmi
2022-07-13 4:53 ` jcgruenhage
2022-07-13 5:04 ` 0x5c [this message]
2022-07-13 5:45 ` jcgruenhage
2022-07-13 5:59 ` lemmi
2022-07-13 6:10 ` 0x5c
2022-07-13 6:29 ` 0x5c
2022-07-13 6:54 ` 0x5c
2022-07-13 6:59 ` lemmi
2022-07-13 6:59 ` jcgruenhage
2022-07-13 17:15 ` [ISSUE] [CLOSED] " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220713050440.UX3Xg0vrQ7VOSHVSgCGuw1as1hSBA8gQMbznMard6iE@z \
--to=0x5c@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).