- From: John Bradley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Jun 2020 14:39:52 +0000
- To: public-webauthn@w3.org
A roaming authenticator not supporting ES256 seems like a bit of a corner case. However I guess someone might make something using a TPM that only supports RS256. The thing is if you don't support ES256 would that authenticator support U2F? If the authenticator doesn't expose U2F I thought the current logic was to ask for UV/clientPin -- GitHub Notification of comment by ve7jtb Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1437#issuecomment-640672268 using your GitHub account
Received on Monday, 8 June 2020 14:39:53 UTC