Re: [webauthn] Add considerations for string truncation. (#1205)

> This is not my understanding with CTAP based on the January publication.

This PR resulting from having implemented this functionality in Chrome. It reflects what future releases of Chrome and (I'm told) Windows will do. It's already the case that with conformant authenticators on the market that one can use Webauthn to create a discoverable credential with a `name` or `displayName` greater than 64 bytes and then get them to return invalid CBOR to future requests due to string truncation. Platforms have to handle this.  

-- 
GitHub Notification of comment by agl
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1205#issuecomment-492652392 using your GitHub account

Received on Wednesday, 15 May 2019 13:23:23 UTC