Implement CTAP 2.1 about opensk HOT 7 CLOSED

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?

from opensk.

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

from opensk.

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

PRs merged for finishing support:

• #254
• #256
• #263
• #265
• #267
• #273

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

from opensk.

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

from opensk.

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

from opensk.

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

from opensk.

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

from opensk.