User Verification spec compliance #47
Unanswered
My1
asked this question in
General Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I have a question about
https://passkeys.dev/docs/reference/known-issues/
This page seems to indicate that solely using the unlocked state as uv=true is not enough.
however there are at least 6 FIDO2 Certified authenticators (granted they are a family on the same software platform) which do exactly the same.
https://github.com/LedgerHQ/app-security-key/blob/main/src/ctap2/ctap2_utils.c#L67-L70
They literally write that they skip a dedicated FIDO2-Level UV process due to them being unlocked using the global unlock, which is similar to the
I would need to check the MDS if there are other FIDO2 devices which UV using an internal menu of sorts, and how they behave but this is essentially for the most part how several similarly set up authenticators that arent certified (Trezor, Mooltipass etc.) also act, and honestly if a certified device is doing it, I dont see why others wouldnt take it as a base model to start with.
maybe the specifics of when and how to UV need to be clarified and checked when going for certification.
All reactions