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

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

>Now consider that things like Meltdown and Spectre have JavaScript PoCs. How is this controversial?

Seems totally irrelevant, since any "legit" site with a $10 certificate will still be able to inject malicious code, either by its operators putting it there directly, or by it being hacked -- whether there's a man in the middle or not. And with something like Spectre out there, https wont do anything.

[ Parent | on HN ]

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

There is a quite big difference between the site injecting it or having it injected via ISP.

[ Parent | on HN ]

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

Yes. That you can trust ISPs (few, large companies) more than random websites.

[ Parent | on HN ]

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

How can you trust someone with a known track-record of violations more than a small website admin?

[ Parent | on HN ]

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

It's easier to trust someone with a "known track-record of violations" than millions of random websites.

[ Parent | on HN ]