New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fido_id does not recognize Yubikeys, Token2, and Solokeys 2 tokens #29278
Comments
abbra
added a commit
to abbra/systemd
that referenced
this issue
Sep 24, 2023
Fixes: systemd#29278 Signed-off-by: Alexander Bokovoy <abokovoy@redhat.com>
abbra
added a commit
to abbra/systemd
that referenced
this issue
Sep 24, 2023
Fixes: systemd#29278 Signed-off-by: Alexander Bokovoy <abokovoy@redhat.com>
I tried to reproduce this on a freshly created Fedora 39 beta VM and it now works for me. I am not sure what was it. For the record, this is how it looks after
I tried few more keys and they also worked. So I'm closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd version the issue has been seen with
254.1
Used distribution
Fedora 39 beta
Linux kernel version used
6.5.3-300.fc39.x86_64
CPU architectures issue was seen on
x86_64
Component
systemd-hwdb, systemd-udevd, udevadm
Expected behaviour you didn't see
fido_id
tool is supposed to recognize FIDO2 USB token and returnUnexpected behaviour you saw
Running
fido_id /sys/path
causes it to use a parent path to the device and then attempt to openreport_descriptor
at that level. Howeverv, the report descriptor is available in a different place which meansfido_id
never gets to open it and fails to recognize the token.I tried with different keys, all of them fail:
Steps to reproduce the problem
Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: