Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by nodesocket on Wednesday July 25, 2018 @04:09AM
(#17607630)
I think one solution would be to make the secure badge more prominent, thus when insecure your eye would be attracted to it. One solution would to be make the entire background color of the secure badge green and invert "Secure" text white.
[ Parent
| on HN ]
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by lozenge on Wednesday July 25, 2018 @04:18AM
(#17607666)
That's basically the approach taken so far and it hasn't worked. Users don't notice these decorations.
Chrome wants to move away from the "Secure" wording because people don't understand what it means, for example, they think it means they can trust the site not to misuse their credit card details.
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by danieldk on Wednesday July 25, 2018 @04:43AM
(#17607780)
Well, it doesn't help that the text (when clicking on 'Secure') says:
Your information (for example, passwords and credit card numbers) is private when it is sent to this site.
To the layman this means: Chrome says it is safe to enter credentials on this site (and not that it just means that it is hard to eavesdrop on the connection), especially that because this does not say anything about the trustworthiness of the site.
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by nsgi on Thursday July 26, 2018 @05:29PM
(#17621375)
How would you phrase it instead, that would communicate the nuances of the issue and allow the lay user to assess the risk?
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by OskarS on Wednesday July 25, 2018 @04:37AM
(#17607755)
I think it should be more prominent than that: make it the size and style of the "do you want to accept notifications?" dialog. It should be unmissable by users that they're on an insecure site.