News for hackers. Stuff that matters.

A comment on Chrome 68 Released: HTTP Sites Marked as “Not Secure”. Parent comment

Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by stephengillie on Wednesday July 25, 2018 @06:33AM (#17608210)
What if someone else uses 192.168.0.5 for their printer too? This just seems incredibly insecure, where I'll have to keep a public record of the private addresses of my devices. Welcome to the Fishbowl.
[ Parent | on HN ]
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by fulafel on Wednesday July 25, 2018 @07:59AM (#17608575)
Yes, RFC1918 addresses are ambiguous, and generally they have this problem, independent of using DNS. You should use IPv6 if you can.

But now you are running TLS, so the address conflict would just yield a cert error. (If the other guy plugged his network or printer into yours, that is)

[ Parent | on HN ]
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by stephengillie on Wednesday July 25, 2018 @11:01AM (#17609784)
Yes, I'm running TLS behind my NAT, where unsecured traffic should be safe. Or should we be using VPN tunnels within our private networks?

And at the same time, I've introduced an internet connection dependency and a 3rd party dependency. What happens when they decide to stop updating that cert, to save money?

[ Parent | on HN ]
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by fulafel on Wednesday July 25, 2018 @12:33PM (#17610533)
You shouldn't treat a SOHO or home network, NAT or not, as secure. There are good reasons why we don't trust the network. Getting compromised is not an "if", it's a "when".
[ Parent | on HN ]