Date: Sat, 20 Aug 2022 16:10:16 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 263790] www/chromium: Unable to use FIDO U2F Message-ID: <bug-263790-28929-aOdUs5DdAE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263790-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-263790-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263790 Ulrich Sp=C3=B6rlein <uqs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uqs@FreeBSD.org --- Comment #19 from Ulrich Sp=C3=B6rlein <uqs@FreeBSD.org> --- No such luck here. After bug #196754 got fixed, this was working fine, but = then it broke Github and Google 2FA logins for some time now, and I'm now on 104.0.5112.79 and have turned on --enable-features=3DU2FSecurityKeyAPI via chrome://flags and it's still busted. But I'm not sure that flag relates to the user-end hardware no longer worki= ng vs. something that websites need to do. :/ What sort of tracing can I turn on to get more information? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263790-28929-aOdUs5DdAE>