Closed Bug 1804979 Opened 1 year ago Closed 1 year ago

FIDO CTAP2 support breaks using FIDO v1 keys with GItHub

Categories

(Firefox :: Untriaged, defect)

Firefox 109
Desktop
macOS
defect

Tracking

()

RESOLVED FIXED
109 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox107 --- unaffected
firefox108 --- unaffected
firefox109 --- fixed

People

(Reporter: amy, Unassigned)

References

(Regression)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

After getting the 109.0a1 update, I tried to login to GitHub with my FIDO Security Key (Yubico) and got to the 2FA page.

Actual results:

The browser warned me that it was expecting a security key, but it was already plugged in. It did not blink.

Expected results:

The security key should have begun blinking, waiting for me to authorize the attestation.

Regressed in https://hg.mozilla.org/mozilla-central/rev/5687d0e50d11.

Also reported as a webcompat issue before coming here: https://github.com/webcompat/web-bugs/issues/115232

OS: Unspecified → macOS
Regressed by: 1752089
Hardware: Unspecified → Desktop
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch

Set release status flags based on info from the regressing bug 1752089

See Also: → 1804972
You need to log in before you can comment on or make changes to this bug.