"Windows Hello" authenticator on Win 11 FIDO Metadata validation alg mismatch issue #393
WorldThirteen
started this conversation in
Troubleshooting
Replies: 1 comment 1 reply
-
Hello @WorldThirteen, you've certainly done your research! I agree with you that this is likely ("simply") FIDO MDS metadata for the Windows Hello AAGUID falling out of sync with the reality of Windows' evolution. If you want to continue to push this forward then I'd say your best bet is to post about this to the fido-dev mailing list and ask when the metadata will get updated to reflect the use of ES256 in Windows: https://groups.google.com/a/fidoalliance.org/g/fido-dev I'm happy to ask there on your behalf as well, it just might take me a few days to get to it. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This topic might seem similar to the #238, but I believe it is most likely a different problem, I've tried to include as much info as requested in #238 (comment).
Brief story
There was a laptop with Win 10 installed, which successfully configured the passkey using SimpleWebAuthn-powered service.
Then Windows was updated to Windows 11 on the same device, and an error occurred trying to re-create the passkey using this service. Direct attestation is requested, and the default FIDO MDS is enabled.
The issue appears in the attestation validation with metadata:
After a brief investigation there is the following information:
08987058-cadc-4b81-b6e1-30de50dcbe96
;rsassa_pkcsv15_sha256_raw
, as correctly and pretty informative displayed in the error above (link for short reaching the FIDO MDS statements https://opotonniee.github.io/fido-mds-explorer);SimpleWebAuthn/packages/server/src/metadata/verifyAttestationWithMetadata.ts
Lines 64 to 116 in 0ab19d8
└── @simplewebauthn/[email protected]
;Additional data:
The WebAuthn registration request request
Attestation object
Attestation object Parsed into JSON representation
I am not familiar with the all procedures required to update the metadata statement in FIDO, so I could be missing something here. I also found out @MasterKale's mention that Windows Hello starting using ES256 here: w3c/webauthn#1757 (comment).
Asking for community help to understand the nature of the issue. I would also appreciate hints of potential mitigation.
Beta Was this translation helpful? Give feedback.
All reactions