Re:Chrome 68 will mark all HTTP sites as “not secure”
by jchw on Friday February 09, 2018 @01:13AM
(#16338275)
Except it works. If it makes you mad, imagine how many other people it makes angry. And aside from recompiling your browser, all you can do is fix the problem and make the browsers happy.
[ Parent
| on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure”
by ori_b on Friday February 09, 2018 @01:44AM
(#16338405)
It makes me want to start serving my sites over Gopher exclusively.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by CamperBob2 on Friday February 09, 2018 @01:35AM
(#16338369)
Except it works.
No, it doesn't, unless your goal is to condition users to ignore yet another warning.
There are downsides to doing that, believe it or not.
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.
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."
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.