Re:Chrome 68 will mark all HTTP sites as “not secure”
by jlarocco on Thursday February 08, 2018 @08:51PM
(#16337270)
Isn't that putting the cart before the horse?
If the connection were HTTPS they could simply block it or redirect it wherever they want to give the same message. An ISP will always be able to MITM the connection.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by Franciscouzo on Thursday February 08, 2018 @09:10PM
(#16337360)
You can't redirect HTTPS traffic unless you have a root certificate or have the private key of the site, and blocking HTTPS traffic would make at least 68% of web traffic not work, so not a real option.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by dingo_bat on Thursday February 08, 2018 @09:43PM
(#16337512)
Can't an ISP's DNS server tell you that https://www.google.com is at 10.10.10.10? And that is an internal server hosting whatever ISP wants.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by Franciscouzo on Thursday February 08, 2018 @09:49PM
(#16337536)
They can, but you will get a certificate error, because the ISP doesn't has a valid certificate for the domain.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by rhencke on Thursday February 08, 2018 @10:00PM
(#16337576)
Exactly. It will show up in any modern browser with a big red "This site is not safe!" type of message if that was to happen. This is one of the reasons Google (and others) so proactively protect the certificate infrastructure so meticulously, and run efforts like https://www.certificate-transparency.org/
https://tools.ietf.org/html/rfc6108
Nobody is affected by this?