Chromium based browser crash when TFA (YubiKey) is being triggered

Since a couple of weeks, chromium related browser are crashing when Two Factor Authentication (TFA) is being triggered.
Means, when I'm trying to login into MS Teams or Outlook (WebApp) and the authentication is calling the MFA, the browser immediately crashes with no error messages.

Using FireFox works out of the box ... while following this information >>CLICK ME<<

I've recently moved from Linux to FreeBSD 14.3 and recently upgraded to 15.0 using Hyprland (Wayland).

Is there anyone who successfully integrated YubiKeys in chromium based browser? Any help is appreciated.
 
Same problem here, and I can pin down exactly where it crashes.

Setup: FreeBSD 15.0-RELEASE, Hyprland (Wayland), chromium-149.0.7827.102, YubiKey 5 (firmware 5.4.3).

When a site triggers the security-key prompt (tested on demo.yubico.com and webauthn.io), Chromium dies instantly with no on-screen error. Launching it from a terminal shows the crash is in the HID layer:

[ERROR:components/device_event_log/device_event_log_impl.cc:200] HID: hid_service_freebsd.cc:382 Failed to set the non-blocking flag on the device fd: Invalid argument (22)
Trace/BPT trap chrome

So it aborts (SIGTRAP) right after the FreeBSD HID backend fails to set O_NONBLOCK on the /dev/uhid* fd (EINVAL, errno 22).

What I've ruled out:
- Not permissions: the key is accessible, fido2-token -L and -I work fine, and /dev/uhid0 is in the u2f group with rw bits.
- Not the key's state: I did a full FIDO2 reset; the key works on demo.yubico.com afterwards. Crash is identical before and after the reset.
- Not the system: Firefox works on the same machine with the same key. Firefox uses authenticator-rs (its own uhid handling), while Chromium uses its C++ HID backend — which is where this fails.

This looks like a bug in the port's hid_service_freebsd.cc rather than anything on our end. Did you find any workaround? Otherwise I'm planning to file it on Bugzilla against www/chromium.
 
Back
Top