Re: [webauthn] truncation to 64-byte upper limit doesn't mention character boundaries

>One issue with truncating like this is that it's not clear to the user agent that a string has been truncated; how would that be handled?

It looks like it _won't_ be handled for the L1 version of the spec. For L2 I think we should collaborate with CTAP to come up with a suitable way for the authenticator to signal to the client what it's able to store, so that the client can do the proper input validation.

-- 
GitHub Notification of comment by emlun
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/973#issuecomment-403760376 using your GitHub account

Received on Tuesday, 10 July 2018 09:29:53 UTC