forked from solokeys/solo1
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Browser rejects signature due to invalid response #58
Labels
bug
Something isn't working
investigate
Reproduce the failing scenario and find the cause
priority:low
Comments
Reproduced locally while testing with webauthn.io, user id xxx (could be found in RK Store data structure). Attaching flash dump for further investigation. Commit: 2.2.0.nitrokey-6-g554c864. Chrome
Chrome log (click me)
|
To do:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
investigate
Reproduce the failing scenario and find the cause
priority:low
Frequency: always with a given account, set up with a couple of FIDO2 tokens registered; not reproducible later on another accounts / after all tokens are removed from the account and added later;
Browsers tested on the same service/account and failing: Chromium 83, Brave 1.13.86 (Chromium: 85.0.4183.102), Vivaldi 3.3;
Browsers working on the same service/account: Firefox;
Priority: low (due to the rare occurrence)
Chromium browser reported bad response from the FIDO2 authenticator, as a cause of rejecting signature from the device. The direct cause is not known due to lack of complete log. The conditions for that check are listed below in the browser's source code, and had to be tested one by one shall the problem would reproduce again.
Usual Webauthn test pages were working on all browsers.
There is also the error message logged into the .xsession-error.log:
Note: to take logs under Chromium run:
Mentioned browser's conditions:
https://github.com/chromium/chromium/blob/894fb9eb56c6cbda65e3c3ae9ada6d4cb5850cc9/device/fido/get_assertion_request_handler.cc#L82-L158
The text was updated successfully, but these errors were encountered: