News for hackers. Stuff that matters.

A comment on Chrome 68 will mark all HTTP sites as “not secure”. Parent comment

Re:Chrome 68 will mark all HTTP sites as “not secure” by jchw on Friday February 09, 2018 @10:08AM (#16340674)
Frankly, if they could just drop plain HTTP support altogether, I'd prefer that. This is more of a friendly compromise.
[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by CamperBob2 on Friday February 09, 2018 @06:32PM (#16344754)
This is more of a friendly compromise.

"Nice open Internet you've got there, no gatekeepers. Be a shame if something were to happen to it."

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by nileshtrivedi on Saturday February 10, 2018 @04:17PM (#16349654)
This is the issue with all systems that use human-friendly naming because someone is in the authority to do the name resolution. This battle was lost when DNS came along.

Not everybody wants to use public keys to refer to everything - even if it is via QR codes.

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by jchw on Friday February 09, 2018 @11:24PM (#16345875)
There were never no gate keepers.
[ Parent | on HN ]