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

Re:Chrome 68 will mark all HTTP sites as “not secure” by josteink on Thursday February 08, 2018 @03:56PM (#16335526)

Only if you use a shitty ISP which tries to MITM you.

So don’t use a shitty ISP that tries to MITM you.

Problem solved. How is that even controversial?

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by Klathmon on Thursday February 08, 2018 @04:32PM (#16335763)

But it's not only if you use a shitty ISP. It's if any hop between you and the server is being shitty. And only 1 or 2 of those can you control as the user.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by shakna on Thursday February 08, 2018 @07:16PM (#16336803)

Having spent four months in a hospital, it isn't just "ISPs" who are the problem.

Rather than the hospital supplying any kind of proper authentication, they MITM the first connection to their WiFi, and logged your IP address as your user. They also required you refresh that connection every half hour or so.

There are a lot of people doing things in really bad ways.

We can't fix all of them, and often we don't have a choice about interacting with them.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by IncRnd on Friday February 09, 2018 @09:09AM (#16340226)

Yep. That's why the name for any one of these is "captive portal".

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by pfg on Thursday February 08, 2018 @04:34PM (#16335772)

Users often have very little choice when it comes to their ISP. Regional ISP monopolies are very much a thing in many countries.

[ Parent | on HN ]