tools: add CLI flag to force FIDO2 #735
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Matching the exisitng -u flag to force U2F. This can be useful for checking that a device works correctly under FIDO2 and does not rely on fallback to U2F.
|
Hi, While we can see how it could be useful for debugging your own implementation, we are not necessarily sure that the tools provided by libfido2 should learn this option. After all, they default to FIDO2 and drop to U2F only if the authenticator does not implement the former. Debug output can be used to clearly see when U2F fallback happens. The output from Thank you for sharing the patch! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Matching the exisitng
-uflag to force U2F.This can be convenient for checking that a device works correctly under FIDO2 and does not rely on fallback to U2F.
Specifically I’m currently investigating a device which should support FIDO2, failing under the CTAP2/FIDO2 mode of another implementation and wanted to cross-check that the device actually works with CTAP2 in libfido2 (it does). I thought this may also be helpful to other so here’s the patch I used including documentation updates.