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?
[ Parent
| on HN ]
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.