https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276697
--- Comment #4 from Christian Weisgerber <na...@freebsd.org> --- (In reply to Christoph Moench-Tegeder from comment #3) The communication with the FIDO/U2F authenticator happens in the main firefox process. I ktraced this for both the working and non-working case. In both cases, firefox successfully opens the correct /dev/uhidN device, initializes the Client-to-Authenticator Protocol, queries the authenticator for its supported features, and receives the response. All of this happens identically in both cases. In the non-working case, firefox then stops: it closes the fd, and exits the thread. In the working case, firefox proceeds to exchange cryptographic messages with the authenticator, and eventually closes the fd, and exits the thread. There is nothing in the initial communication with the authenticator that would explain the different behavior. The authenticator's responses are identical. -- You are receiving this mail because: You are the assignee for the bug.
