News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by Skunkleton on Friday February 09, 2018 @02:39PM (#16343213)
Chrome could easily turn this warning off for private network address blocks. I wonder if this has been discussed, and if so why was it rejected?
Re:Chrome 68 will mark all HTTP sites as “not secure” by nybble41 on Friday February 09, 2018 @06:14PM (#16344651)
Networks which use the private network address blocks are not necessarily trusted networks (consider open Wi-Fi hotspots). Also, private networks do not necessarily use private network address blocks—intranets frequently use publicly-routable IP addresses where possible, as it simplifies linking physically distinct intranets. With IPv6 eliminating the scarcity of public addresses we can expect this to become much more common, even among home users.
Re:Chrome 68 will mark all HTTP sites as “not secure” by nsgi on Tuesday February 13, 2018 @02:19PM (#16369871)
If you're using a publicly-routable IP address why not use a publicly-routable hostname and get a certificate for it?
Re:Chrome 68 will mark all HTTP sites as “not secure” by nybble41 on Wednesday February 14, 2018 @11:00AM (#16376714)
The fact that the IP address is publically routable does not imply that the server is actually reachable from the public Internet—that depends on the firewall.

You can associate public hostnames with private-range IP addresses as well, and obtain certificates for them. The main point was that the use of private, non-routable IP addresses does not imply that the network is trusted, and thus is not sufficient reason to exempt the server from securely identifying itself.

Re:Chrome 68 will mark all HTTP sites as “not secure” by Skunkleton on Sunday February 11, 2018 @12:35AM (#16351360)
Yeah, that is a fair point.