Skip to content
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

Implement CTAP 2.1 #106

Closed
kaczmarczyck opened this issue May 6, 2020 · 7 comments
Closed

Implement CTAP 2.1 #106

kaczmarczyck opened this issue May 6, 2020 · 7 comments
Assignees
Labels
tracking List of things to do

Comments

@kaczmarczyck
Copy link
Collaborator

The review draft for CTAP 2.1 adds new commands and requires seom changes in the old ones.
https://fidoalliance.org/specs/fido2/fido-client-to-authenticator-protocol-v2.1-rd-20191217.html
We want to support new features like deleting resident keys.

Our access to a more recent version of CTAP 2.1 allows us to prototype those new features and give feedback on the command design. This issue tracks our progress. Please be aware that these commands are still exprimental and the implementation can change in the future. Do not rely on them!

@kaczmarczyck
Copy link
Collaborator Author

The current implementation in the develop branch follows review draft 2 of CTAP 2.1.

PRs merged for finishing support:

Current WIP:
#274

Missing work:

  • updating all existing command algorithms
  • alwaysUv for MakeCredential and GetAssertion
  • toggleAlwaysUv in authenticatorConfig
  • enterprise attestation
  • enableEnterpriseAttestation in authenticatorConfig
  • PIN Protocol V2
  • all potential changes after review draft 2

@kaczmarczyck
Copy link
Collaborator Author

Features around alwaysUv, enterprise attestation and PIN protocol V2 (PRs for the latter: #293, #295, #296) are implemented. Missing work:

  • remaining updates for existing command algorithms
  • missing changes from review draft 3

@kaczmarczyck
Copy link
Collaborator Author

CTAP2.1 changes are complete with #297 and #299 (to be reviewed as of now). Not all features are thoroughly tested yet.

@Sami32
Copy link

Sami32 commented Aug 27, 2022

Any update on this?

It seem that features have been tested and that CTAP 2.1 get its final version:
https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-errata-20220621.html

@kaczmarczyck
Copy link
Collaborator Author

Hi! We haven't noticed any problems with our implementation of CTAP 2.1 yet. It will take more time for an official release, but you can try out the develop branch if you are curious about the current state. Is there anything specific you are interested in?

@Sami32
Copy link

Sami32 commented Sep 10, 2022

Hi!
Sorry for my late answer.
Thanks for the information +1
I'm mostly interested in the management of discoverable credentials.

Note:
https://eprint.iacr.org/2022/1029

@kaczmarczyck
Copy link
Collaborator Author

Management of discoverable credentials works with e.g. Chrome (chrome://settings/securityKeys) on develop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracking List of things to do
Projects
None yet
Development

No branches or pull requests

2 participants