-
-
Notifications
You must be signed in to change notification settings - Fork 629
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
[Epic] Implement full WebAuthn/FIDO2 #39
Comments
Mainly we are interested in parsing Application+User data from the protocol and showing that on the display. |
Pull request: #204 Regression testing: Focus on U2F and Cardano. Ensure that logging in with a U2F credential that was created prior to firmware upgrade works correctly. |
The FIDO2 implementation for Trezor T is currently undergoing review #394. If all goes well, we can release this in September. There are several options for the release:
I would prefer option 3 as it is the safest and cleanest solution. The full release of FIDO2 can happen in October. From the marketing perspective there is no rush, because in September the focus will be on Shamir Backup. I expect @prusnak to make the final decision on this and @ZdenekSL to communicate the decision with marketing. |
The only thing missing is #245, which is tracked in its own issue. Closing. |
@Quiark That's a bug on our website which will be fixed soon. Currrently, we don't plan to support FIDO2 on Trezor One. |
What a shame ! |
Currently, we do U2F, but let's expand the functionality to full WebAuthn (aka FIDO2) support.
Subtasks:
#245 Add support for FIDO2 resident credentials
#206 Implement FIDO2 credential selection
#205 Redesign FIDO2 credential ID format
#31 Modify U2F/webauthn app to use Keychain
The text was updated successfully, but these errors were encountered: