News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by jhanschoo on Friday February 09, 2018 @12:28AM (#16338100)
Nobody is giving up freedom for security; you can still visit HTTP sites if you want to, its just going to be treated as unsafe by default.

As other commenter noted, Comcast has been observed to inject content to its customers; would you rather that on HTTP or that you run HTTPS?

Re:Chrome 68 will mark all HTTP sites as “not secure” by Santosh83 on Friday February 09, 2018 @01:18AM (#16338300)
When a highway is plagued by bandits, the govt must go after the bandits and put them away, not close the highway or turn into a cramped tunnel made of armoured steel with only one narrow lane.
Re:Chrome 68 will mark all HTTP sites as “not secure” by hagbarth on Friday February 09, 2018 @05:32AM (#16339235)
So which central govt should we trust to "put the bandits away" on the internet?
Re:Chrome 68 will mark all HTTP sites as “not secure” by Santosh83 on Friday February 09, 2018 @07:03AM (#16339561)
I'm saying that instead of doing away with plain-text protocols, maybe national govts can each regulate their ISPs to stop injecting content into the bits they transmit? That would go a long way towards increase of privacy. As for bad state (sponsored) actors, I doubt https can really stop them doing what they want, especially not the big ones.
Re:Chrome 68 will mark all HTTP sites as “not secure” by deadbunny on Friday February 09, 2018 @09:39AM (#16340434)
> maybe national govts can each regulate their ISPs to stop injecting content into the bits they transmit?

Good one. Next you'll be telling me that those very same companies don't spend billions on getting the laws written the way they want.

Sure you could try the top down approach where everyone has the best intentions but that's not going to happen, in the meantime I'm installing bulletproof windows in my car.

Re:Chrome 68 will mark all HTTP sites as “not secure” by andybak on Friday February 09, 2018 @03:23AM (#16338724)
That's a very narrow view of the options available for law enforcement. Sometimes "going after all the bad guys" is a terrible strategy.
Re:Chrome 68 will mark all HTTP sites as “not secure” by ajnin on Friday February 09, 2018 @09:18AM (#16340304)
Some Javascript, HTML or HTTP features are available on HTTPS only. Even things like Brotli stream compression which have no security implications. So some liberty is definitely taken from users who wish to use insecure connections for whatever reason.