Thread of 4 posts
Oh, eff. I have no idea how this is to be fixed, but U2F seems to have broken on Firefox 114 (and Chrome and so on) on #freebsd
https://bugzilla.mozilla.org/show_bug.cgi?id=1737205
Apparently we were relying on a deprecated API?
Do #openbsd folks have this figured out?
Ok, thanks to feedback I got and to some reminder that things have changed quite a bit on #freebsd CURRENT, I took a deeper look:
- firefox-esr is at 102.12.0 on the repositories, which should still support legacy u2f
- tests showed that that too, was failing
So that seemed fishy, and I forced a fresh CURRENT upgrade based on the changelogs, and tried again with firefox-esr.
That still didn't work, but I remembered I had taken a look at a #freebsd PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265528
and had just tried (while trying to debug the u2f issue) hw.usb.usbhid.enable=1
So I reverted that, unplugged and pugged again, and everything worked as expected.