Re: [webauthn] Adding flexibility in client origin scheme validation to align with real world implementations (#2018) from Barry Pederson via GitHub on 2024-02-15 (public-webauthn@w3.org from February 2024)

From: Barry Pederson via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Feb 2024 01:28:13 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-1945219788-1707960490-sysbot+gh@w3.org>

Is this going to cover the case of having names in a `/etc/hosts` file like

    127.0.0.1 foo.localhost
    127.0.0.1 bar.localhost 


and then trying to access `http://foo.localhost` or `http://bar.localhost`?  I'm doing this on my development laptop with several sites.

Seems like those are considered Secure Contexts elsewhere.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 15 February 2024 01:28:15 UTC