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

@agl, AIUI, are you saying that if the RP script invokes display of these strings, the browser will "UTF-8 validate the data and handle abrupt truncation", before displaying the strings?

this is just chrome's standard handling of displayed strings ?

what do you mean by "handle abrupt truncation"?

if a utf-8-encoded string, containing multi-byte encoded chars, was truncated at an arbitrary byte boundary, does the validation process catch that?

what is the behavior if the string is "corrupted" from a UTF-8 correctness perspective?

thx.

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

Received on Thursday, 12 July 2018 21:00:31 UTC