Solokeys Solo v2 fido key not supported in linux snap builds
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: tmciolek, Unassigned)
References
(Blocks 1 open bug, )
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
Issue occurs on Ubuntu 22.04.
It appears that the new Solokeys Solo v2 keys (VID:PID = 1209:beee ) are not present in the relevant u2f device listings in /etc/udev/rules.d/70-snap.firefox.rules file.
- install Firefox snap on Unbuntu
- navigate to a fido/u2f secured login page and authenticate
- firefox asks for u2f token to be plugged in
- plug in Solo v2 u2F token
Actual results:
authentication times out waiting for the token. Token is not detected.
Expected results:
Token should be recognised and should change LED colour to provide a response to the u2f challenge. this does not happen
issue can be remediated by adding VID/PID of 1209/beee to the /etc/udev/rules.d/70-snap.firefox.rules file
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
lsusb -v output :
Bus 001 Device 013: ID 1209:beee Generic Solo 2 Security Key
based on this, manually adding the following stanza:
SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="beee", TAG+="snap_firefox_firefox"
to /etc/udev/rules.d/70-snap.firefox.rules appears to fix the issue
|
||
Comment 3•2 years ago
|
||
This was fixed upstream in snapd 2.56 which seems to have shipped: https://github.com/snapcore/snapd/commit/9c94b67eb4fe64bd5fe26d8e1968f73f957d1cf0
Marking as FIXED, feel free to reopen if you still repro even with this version.
|
|
||
Updated•2 years ago
|
having received snap update of firefox this morning my time (firefox 101.0.1-1) the issue appears to have been resolved. All of my security keys work as expected.
many thanks for your efforts
Description
•