1. YubiKey is still not released by Fedora after boot when the YubiKey is inserted at the time of boot up with the result that `gpg --card-status` fails (a problem from Fedora Silverblue 39). `systemctl restart pcscd' is still needed to get `gpg --card-status` to recognise the YubiKey. Windows does not do this. 2. `~/.gnupg/scdaemon.conf` setup by user in Fedora 39 seems to be gone in Fedora 40? Pinentry errors in Kleopatra are emitted in Fedora 40 even when `gpg --card-status` is fine, requiring re-creation of the `scdaemon.conf` file with the entry 'reader-port Yubico Yubi` and a reboot (after which Kleopatra is back to normal). see (https://support.yubico.com/hc/en-us/articles/360013714479-Troubleshooting-Is...)
Fedora 40 beta is very impressive overall!
On Wed, 2024-03-27 at 19:45 +0000, Fraser Tajima wrote:
- YubiKey is still not released by Fedora after boot when the YubiKey is inserted at the time of boot up with the result that `gpg --card-status` fails (a problem from Fedora Silverblue 39). `systemctl restart pcscd' is still needed to get `gpg --card-status` to recognise the YubiKey. Windows does not do this.
- `~/.gnupg/scdaemon.conf` setup by user in Fedora 39 seems to be gone in Fedora 40? Pinentry errors in Kleopatra are emitted in Fedora 40 even when `gpg --card-status` is fine, requiring re-creation of the `scdaemon.conf` file with the entry 'reader-port Yubico Yubi` and a reboot (after which Kleopatra is back to normal). see (https://support.yubico.com/hc/en-us/articles/360013714479-Troubleshooting-Is...)
Fedora 40 beta is very impressive overall!
Could you please report these as bugs against the relevant packages? They seem very domain-specific and you're more likely to get a useful response from a bug report that will be assigned to a person who knows something about this domain, I think :)
Thanks!
-
Adam Williamson -
Fraser Tajima