- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Dec 2022 00:01:07 +0000
- To: public-webauthn@w3.org
@nicksteele The thing is, as an RP we already have the ability to discriminate authenticators by rejecting attestations. We already are in *exactly* the situation described. The difference is where the UI/UX onus is placed - on the RP to "post attestation failure" document "hey, we don't support that device". Or if we can provide hints to a browser to say "hey just don't show that authenticator as being allowed to participate in this ceremony". This isn't about allowing RP's to discriminate authenticators - we can already do that. This is about having browsers display a nicer UI/UX that an authenticator is about to be rejected during a ceremony. -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1816#issuecomment-1353901950 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 December 2022 00:01:12 UTC