-
Notifications
You must be signed in to change notification settings - Fork 135
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
Not following the Passkey standard propely, breaking keepassxc passkeys #2560
Comments
Tofixrs
changed the title
Not following the WebAuthN standard propely, breaking keepassxc passkeys
Not following the Passkey standard propely, breaking keepassxc passkeys
Aug 19, 2024
Hi @Tofixrs Thanks for the report. We will look into it. |
frederikrothenberger
added a commit
that referenced
this issue
Aug 20, 2024
According to the WebAuthn spec the challenge _should_ be at least 16 bytes. So far it was 9. Apparently, KeePassXC verifies the challenge length and refuses to sign shorter values. This changes the length to 16 bytes which should address the problem. Closes #2560.
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 20, 2024
According to the WebAuthn spec the challenge _should_ be at least 16 bytes. So far it was 9. Apparently, KeePassXC verifies the challenge length and refuses to sign shorter values. This changes the length to 16 bytes which should address the problem. Closes #2560.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Was trying to register to open chat, but it kept failing, looked into the console greeted with this message
Thought it was a keepassxc bug but the developer told me that challange needs to be atleast 16 bytes in length as were ii uses only 9
Since on linux i dont have any other way of using passkeys (not that i am aware of) this blocks me out of websites using it
The text was updated successfully, but these errors were encountered: