Closed
Bug 1434451
Opened 7 years ago
Closed 6 years ago
Add BrowserSetting for FIDO U2F support
Categories
(WebExtensions :: General, enhancement, P3)
WebExtensions
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jcj, Unassigned)
References
()
Details
(Whiteboard: [u2f][browserSettings][privacy])
FIDO U2F (Bug 1065729) is disabled by default, in favor of W3C Web Authentication. There's significant and ongoing interest in users enabling it via about:config [1][2] (and many more...).
It'd be nice for someone to produce a web extension that turned on FIDO U2F support by flipping the "security.webauth.u2f" pref, letting users who are knowledgeable about the limitations of our support use legacy websites.
I believe this would be done with a BrowserSetting in similar vein to the websites.resistFingerprinting extension point.
[1] https://www.yubico.com/2017/11/how-to-navigate-fido-u2f-in-firefox-quantum/
[2] https://www.reddit.com/r/firefox/comments/7dbcbl/firefox_quantum_comes_with_u2f_support/
Updated•7 years ago
|
Priority: P3 → --
Whiteboard: [u2f] → [u2f][design-decision-needed]
Comment 1•7 years ago
|
||
:jcj I caught up a bit on U2F and I agree, this makes sense as a browserSetting API for WebExtensions. I'm going to add it to the API backlog.
Priority: -- → P3
Whiteboard: [u2f][design-decision-needed] → [u2f][browserSettings]
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•6 years ago
|
Whiteboard: [u2f][browserSettings] → [u2f][browserSettings][privacy]
Reporter | ||
Comment 2•6 years ago
|
||
Now that this is on by default, this is pretty much unnecessary.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•