Skip to content
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

U2F Zero fails to authenticate on Fedora 35 #104

Open
quignogs opened this issue Dec 28, 2021 · 0 comments
Open

U2F Zero fails to authenticate on Fedora 35 #104

quignogs opened this issue Dec 28, 2021 · 0 comments

Comments

@quignogs
Copy link

I have a U2F zero, delivered in Feb 2018 to the UK. It may be a bad one, but in 2018 I successfully registered it with Google 2FA on Firefox and used the key several times to authenticate over the next year or so.

I haven't used the key since then, but yesterday I tried to set up pam-u2f for login.

Registering works fine: pamu2fcfg -u zoom >> /etc/u2fkeys.
The key's led flashed, I pressed the button and the output seems OK.
But login authentication failed.

I tried to use the key to authenticate to Google yesterday; that now doesn't now work. Earlier today, I successfully registered the key for 2FA with github and on my personal nextcloud instance. Registration works fine, but Firefox won't authenticate. When I try, Firefox pops up a window which says <server> wants to authenticate you using a registered security key. You can connect and authorise one now, or cancel. But I don't get an option to use the key, only the cancel button.

So it seems that both Firefox and pam are doing the same thing, which suggests that the cause lies in either user space libraries or the kernel.

I can reproduce the login problem with pamtester: here is a redacted debug log. I'm removing all the sensitive data, but what I see looks convincing.

The hid-u2fzero module loads OK. I see no problem with e.g. selinux denying access to anything: this is what syslog sees while pamtester runs. It would seem that there is an I/O problem, but only after a couple of exchanges are completed. I understand that the problem with the bad batch was with command 0x07; I see only 0x06 and 0x03.

Ideas? Is there a sanity check for U2F Zero which can pin down where the problem is? I assume that pam-u2f hasn't suddenly stopped working and that Yubi or Nitro keys are probably OK, but I don't have either to hand for comparison. None of the bad key workarounds for pam-u2f such as nodetect, cue or manual affect this failure.

$ firefox --version
Mozilla Firefox 95.0.2
$ uname -r
5.15.11-200.fc35.x86_64
$ rpm -qa|grep u2f
pam-u2f-1.2.0-2.fc35.x86_64
pamu2fcfg-1.2.0-2.fc35.x86_64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant