Bug 468681

Summary:	Firefox U2F keys support problem
Product:	[KDE Neon] neon	Reporter:	Chris <stivi>
Component:	Packages User Edition	Assignee:	Neon Bugs <neon-bugs>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	bugs, jr, lego37yoon, neon-bugs, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Output for U2F Firefox teest on https://u2f.bin.coffee/ webpage

Description Chris 2023-04-19 11:18:14 UTC

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

Comment 1 Simon Brown 2023-10-12 09:51:17 UTC

*** Bug 469787 has been marked as a duplicate of this bug. ***

Comment 2 Simon Brown 2023-10-12 09:58:41 UTC

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.

Comment 3 Simon Brown 2023-10-12 10:05:29 UTC

I have just tested with the tarball release from Mozilla.org and my key works correctly with that package

Comment 4 Simon Brown 2023-10-12 10:08:25 UTC

It is app armour. 

sudo aa-disable usr.bin.firefox

allows my security key to work as it should.

Comment 5 Carlos De Maine 2025-09-20 09:35:26 UTC

Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!