-
Notifications
You must be signed in to change notification settings - Fork 10
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
Reject rk option in getAssertion #31
Comments
This was referenced Jul 7, 2023
robin-nitrokey
added a commit
to robin-nitrokey/fido-authenticator
that referenced
this issue
Jul 10, 2023
The getAssertion command does not use the rk option so we return an InvalidOption error if it is set. Fixes: trussed-dev#31
nickray
pushed a commit
to robin-nitrokey/fido-authenticator
that referenced
this issue
Sep 13, 2023
The getAssertion command does not use the rk option so we return an InvalidOption error if it is set. Fixes: trussed-dev#31
nickray
pushed a commit
to robin-nitrokey/fido-authenticator
that referenced
this issue
Sep 13, 2023
The getAssertion command does not use the rk option so we return an InvalidOption error if it is set. Fixes: trussed-dev#31
nickray
pushed a commit
that referenced
this issue
Sep 13, 2023
The getAssertion command does not use the rk option so we return an InvalidOption error if it is set. Fixes: #31
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The getAssertion command does not use the
rk
option so we should return anInvalidOption
error if it is set.The text was updated successfully, but these errors were encountered: