4 ms·
I don't understand how it has taken them so long to add it natively... they just shipped FLAC audio support but still don't care about U2F?
by artursapek 10y ago
I don't understand how it has taken them so long to add it natively... they just shipped FLAC audio support but still don't care about U2F?
- deleted 10y ago[deleted]
- callahad 10y agoBarring unforeseen complications, U2F support should land in stable Firefox this year. The tree of bugs to follow is rooted at https://bugzilla.mozilla.org/show_bug.cgi?id=1065729 https://bugzilla.mozilla.org/show_bug.cgi?id=1065729
- cesarb 10y agoFLAC audio support is simpler, it's just adding a self-contained FLAC decoding library, and wiring it to the already-existing audio code. For U2F, they have to write code to interact with the operating system USB API (for each operating system), plus the main U2F code, plus a Javascript API, all while taking care to not cause any new privacy leaks or worse. If you want to follow, the main bugzilla item seems to be this one: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1065729&hide_resolved=0 https://bugzilla.mozilla.org/showdependencytree.cgi?id=10657...
- wahern 10y agoThe USB part is the simplest part. U2F uses USB HID for messaging. That's probably less complicated than using the D-Bus interface. And anyhow there's probably already an open source library for U2F USB HID clients. Mozilla will probably use whatever Chrome is using. The real complexity is in exposing the interfaces through Javascript and orchestrating all the GUI components. In fact, U2F doesn't even require a hardware token. It was designed so browsers could implement everything in software to hasten adoption.
- baq 10y agoholy crap. Reported: 2014-09-10 16:07 PDT by Axel Nennker Modified: 2017-01-26 08:24 PST (History) CC List: 419 users (show)
- mtgx 10y agoYeah, Google implemented it in Chrome in 2014...I guess it's just not a high priority for Mozilla right now.