Created attachment 158212 [details] Output for U2F Firefox teest on https://u2f.bin.coffee/ webpage On standard default installed version of Firefox there is problem with U2F keys support. All works ok with Falcon. On old Kde Neon (based on Ubuntu 20.04 LTS), with the same version of Firefox, all works good. After uninstall Firefox standard package version and install snap version, U2F is working. So looks like the problem is in Firefox from deb packet. STEPS TO REPRODUCE 1. Enable below options in Firefox settings (about:config) security.webauth.u2f=True security.webauth.u2f_enable_softtoken=True 2. Insert U2F key to usb 3. Enter into page: https://u2f.bin.coffee/ and click test buttons. OBSERVED RESULT There is error (example on the screenshot) EXPECTED RESULT Should communicate properly, without errors, with U2F key. SOFTWARE/OS VERSIONS Linux/KDE Plasma: The newest version with all updates (19 April 2023) ADDITIONAL INFORMATION Firefox: 112.0.1 (64 bits), arm architecture I used Yubico hardware U2F keys for test: YubiKey 5 NFC, YubiKey 5 Nano and
*** Bug 469787 has been marked as a duplicate of this bug. ***
This bug is still present in Firefox 118.0.2 on a clean install of Neon. My yubikey works successfully with Chromium from a PPA, but with Firefox it behaves as if it were disabled. I have compared against another machine that runs Kubuntu 22.04 with the same mozilla team package and it works successfully. So it isn't the package, but the environment. I have verified that the about:config webauthn settings are the same on both machines. I had to set apparmor to complain with firefox in order to get my password manager to work, so I wonder if this is a confinement problem? Marking as confirmed as it affects at least three people.
I have just tested with the tarball release from Mozilla.org and my key works correctly with that package
It is app armour. sudo aa-disable usr.bin.firefox allows my security key to work as it should.