Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by robin_reala on Wednesday July 25, 2018 @05:22AM
(#17607937)
What’s to deal with? It’s still the same as before: not secure.
[ Parent
| on HN ]
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by y0ghur7_xxx on Wednesday July 25, 2018 @06:02AM
(#17608106)
> What’s to deal with? It’s still the same as before: not secure.
But there is no meaningful way to make it secure. So marking it not secure creates just noise.
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by dullgiulio on Wednesday July 25, 2018 @06:43AM
(#17608255)
Well, also the "delayed" notice at the gate of an airport makes noise.
It's informative: you might not be able to do anything about it, but you should know it anyway.
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by y0ghur7_xxx on Wednesday July 25, 2018 @07:57AM
(#17608571)
There is a difference between an information and a warning. If I am entering information on an unencrypted connection on the internet I want a warning. And I don't want to get accustomed to that warning, because if it happens I want to be alerted.
If the same thing happens in my local lan I don't want the same warning, because if I get the same warning I will start to ignore it, and not only when I'm in my local lan.