From: jcgruenhage <jcgruenhage@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:45:18 +0200 [thread overview]
Message-ID: <20220713054518.R1LcHtHQTCjQVEo7JMRLAzVxrEHcqWsjp3v9nSkkooA@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: 1153 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/issues/38034#issuecomment-1182791111
Comment:
@0x5c I think the situation isn't as bad as you make it out to be: I'm running GnuPG 2.3.7 on Void, and I'm using a Yubikey 5 without any of those workarounds just fine. I think what masked this issue for me is having ykpers installed, which ships udev rules for current yubikeys as well. My current plan for now would be:
- split out the yubikey udev rules from ykpers into a separate package, add dependency on that to gnupg. This should be good enough for most users, and it's an easy enough fix that I can push out today.
- investigate the situation with the Debian udev rules. From the thread linked above, it seems like NixOS had success with using those udev rules, and I'll investigate how other distros (especially Fedora and it's derivates) are handing this. I'd assume that we can package some set of udev rules to make this just work for nearly everybody.
- I'll add some documentation for this on docs.voidlinux.org, if there's anything still left to do for users, but I kinda doubt it.
next prev parent reply other threads:[~2022-07-13 5:45 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
2022-07-13 5:45 ` jcgruenhage [this message]
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=20220713054518.R1LcHtHQTCjQVEo7JMRLAzVxrEHcqWsjp3v9nSkkooA@z \
--to=jcgruenhage@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).