That does imply AppArmor is the issue with that denial; `authenticator-
rs` requires hidraw access to the relevant devices.
https://github.com/amluto/u2f-hidraw-policy is the package used by other
linuxes, I don't know the equivalent for Debian.
--
You received this bug notification because you
Tested this today, via the github site, and both authentication and the
registration of a new key fails. Logging I can find related to this in
/var/log/syslog is:
Jan 31 09:53:13 hyperion kernel: [605631.650563] audit: type=1400
audit(1580428393.744:1863): apparmor="DENIED" operation="open"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741768
Title:
Still fails on Ubuntu 18.04.1 with 61.0.1+build1-0ubuntu0.18.04.1, while
it works under chromium-browser 68.0.3440.106-0ubuntu0.18.04.1.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still fails with 59.0.2+build1-0ubuntu0.16.04.1. Does anyone care about
their users' security at Canonical?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741768
Title:
U2F FIDO authentication
Still fails with 58.0+build6-0ubuntu0.16.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741768
Title:
U2F FIDO authentication doesn't work
To manage notifications about this bug go to:
Hi jc-moz,
I initially thought so, but switched AppArmor to complain mode (rather
than enforce) and got the same results (also the Mozilla-built Chromium
works fine). Current AppArmor status:
$ sudo apparmor_status
[...]
17 processes have profiles defined.
9 processes are in enforce mode.
Hi, I'm one of the Firefox developers working on our FIDO U2F device
support.
Since this works with the Mozilla-built Firefox but not the Canonical
one, I think it's an AppArmor (or similar) setting prohibiting firefox
from reaching libudev or the udev device paths on disk.
--
You received this
