Chrome 68 will mark all HTTP sites as “not secure”

Re:Chrome 68 will mark all HTTP sites as “not secure” by dredmorbius on Saturday February 10, 2018 @12:07AM (#16345989)

Which itself raises several questions:

1. Should most people have access to a domain they control?

2. Should there be a standard for nonroutable / nonpublic domains? (.lan and .localdomain are two of which I'm generally aware)

3. How should browsers deal with hosts and/or domains which are not and can not be on the public Internet?

4. How the hell did we get into this mess?

I'm kicking around the notion of relaxing various aspects of the problem domain and seeing where we end up. It's mind-numbingly bad, though.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by dredmorbius on Saturday February 10, 2018 @01:35PM (#16348736)

Also: if we don't use the domain registration system to proxy for individual sites and presence on the Internet, then what alternatives might be substituted?

Note that domains don't solve the problem of a third-party controlling your point-of-access or presence, they only move it elsewhere.

[ Parent | on HN ]