Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 May 2022 12:25:10 +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-wzDy2NcPAa@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

--- Comment #15 from Peter Jeremy <peterj@FreeBSD.org> ---
This still relates to 101.0.4951.64.  I'm building 101.0.4951.67 and will
provide an update later.

After explicitly enabling `Enable the U2F Security Key API` then I can use =
my
security key with Github.

Unfortunately, I still can't add a security key to my Google account: I get=
 to
the popup:
"
Add a security key
You=E2=80=99ll see instructions in your browser window for adding your key =
to your
account
"
and the security key starts flashing.  If I tap it, it stops flashing but it
there are no "instructions" and the popup keeps spinning.  If I cancel and
retry then I get a popup:
"
Couldn=E2=80=99t connect
Remove your key and reconnect it. Then try again.
"

Removing and reconnecting the key doesn't help.

--=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-wzDy2NcPAa>