-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Hello - Mismatch between ECCParameters in pubArea and credentialPublicKey #222
Comments
Yes it can still be reproduced on Windows 11 22H2, I will get a screenshot of that as soon as possible. I'm using 0.9.4 of the library, should I upgrade to at least 0.10.x? It works just fine for Windows 11 23H2 as far as I tested. |
@aseigler I'm sorry, I noticed this particular one has been using an older version. In which version was it fixed? Probably doesn't have the fix you're talking about. |
Whew, you had me there for a second. Pretty sure this got fixed in #43, library version 0.4.0 or later, which is when the test for this particular case got added. |
In this particular one was using github.com/duo-labs/webauthn v0.0.0-20220122034320-81aea484c951 At that moment I was using duo-labs still, so probably doesn't have all these fixes mentioned above. I think is fine to close this as is a false positive. So we can close this issue, as there is no issue :) |
Sounds good to me! Thanks for the followup! |
Version
0.9.4
Description
Attestation bug with Direct & TPM on Windows Hello (Windows 11 22H2).
Searching found it was reported in another library too:
MasterKale/SimpleWebAuthn#238
Reproduction
Trying to enroll Windows 11 22H2 Hello authenticator with
Attestation=Direct
AuthenticatorType=Platform(TPM)
It ends in "Mismatch between ECCParameters in pubArea and credentialPublicKey" error but it should work.
Expectations
Should enroll the device successfully.
Documentation
No response
The text was updated successfully, but these errors were encountered: