- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Jan 2019 11:56:43 +0000
- To: public-webauthn@w3.org
@dwaite That's a good point. Under the assumption that authenticators never share any of their secrets with the outside world - e.g., by allowing to sync a wrapping key with another device - there should be nothing a server-side-resident key can do that a client-side-resident key cannot, so there shouldn't be much reason for an RP to ever prefer a server-side-resident key. And if we remove that assumption, then the authenticator could sync the credential private key just as well as a wrapping key, so the same conclusion should hold in that case. On the other hand, there is good reason for an _authenticator_ to prefer server-side-resident keys if it has limited key storage capacity. But adding the option for the RP to forbid client-side-resident keys does not in any way restrict the authenticator's option to create a server-side-resident key. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1149#issuecomment-459318129 using your GitHub account
Received on Thursday, 31 January 2019 11:56:44 UTC