Re:Chrome 68 will mark all HTTP sites as “not secure”
by CamperBob2 on Friday February 09, 2018 @12:37AM
(#16338132)
It's actually not so complicated: obviously, there's nothing actionable for the user to do here. The message is for the user, but only indirectly: it's there to push developers into better practices
So it's the online equivalent of plastering Warning: Contains chemicals known to the state of California to cause cancer all over everything from gas pumps to gerbils.
Yeah. Real useful.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by icebraining on Friday February 09, 2018 @01:34AM
(#16338364)
If 99.9% of companies could remove those carcinogenic chemicals without reducing the value of the products, I would support that warning too.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by CamperBob2 on Saturday February 10, 2018 @06:58PM
(#16350343)
Even if cancer rates were more or less completely uncorrelated to the presence and/or usage of those products? Congratulations, you've raised the social noise floor for no good reason.
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.
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.
It's actually not so complicated: obviously, there's nothing actionable for the user to do here. The message is for the user, but only indirectly: it's there to push developers into better practices. Your boss may not care about encryption or privacy, but definitely will care about hundreds of phone calls asking why they are warned that the form is insecure when they try to login.
With plenty of obscure pages accepting everything from passwords to credit card numbers on plain HTTP pages, this is important. There may not be someone browsing the page knowledgeable enough to catch this, but if any end user can know what they're doing is wrong, then it's much more likely it will be discovered.
While mostly not actionable directly for users, one thing a user can, and probably should, do is close the page, if they can.