- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 May 2017 15:11:25 +0000
- To: public-webauthn@w3.org
I am fairly sure this issue is essentially addressed by the browser processing paths (spec'd in [URL](https://url.spec.whatwg.org/) and [HTML](https://html.spec.whatwg.org/)), and by the time one runs either of the webauthn algorithms (createCredential, getAssertion), the origin's effective domain is already canonicalized to be an ascii domain. @jyasskin, @bzbarsky ? -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/167#issuecomment-303754824 using your GitHub account
Received on Wednesday, 24 May 2017 15:11:32 UTC