Re: [webauthn] explain challenge's security importance and use in both registration and authentication operations

@mikewest:
>  y'all consider requiring the value to be a base64-encoded DOMString, and doing the decoding/bufferizing as part of the makeCredential and getAssertion algorithms? 

no, we did not think of that -- yes, I'm thinking your suggestion is the way to go -- thanks!


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

Received on Tuesday, 18 April 2017 16:42:17 UTC