Re: Proposal: Marking HTTP As Non-Secure
"'Chris Palmer' via blink-dev" <[email protected]> Fri, 29 Jan 2016 15:02:58 -0800
| Newsgroups | gmane.comp.web.blink.devel,gmane.comp.web.chromium.security.devel,gmane.comp.mozilla.security |
|---|---|
| Message-ID | <CAOuvq21DUSZLLG6X1vkB3fhSqWG0XLrm5vNwHz-=twO5aG3dqw@mail.gmail.com> |
On Fri, Jan 29, 2016 at 1:09 PM, <[email protected]> wrote: You would be much better advised to create proactive mechanisms for > detecting suspicious activity (man-in-the-middle attacks) and alerting when > there really is a bonafide threat That is exactly what HTTPS is. , as opposed to creating signal pollution in your UX. > I leave you with this: > > http://image.shutterstock.com/z/stock-photo-street-intersection-congested-with-street-signs-57695734.jpg Currently, Chrome (and most other browsers) show only the equivalent of the traffic light. We propose to wire up the red lamp. (Recently, we unhooked the yellow lamp, precisely because a proliferation of signals confuses and annoys people: https://googleonlinesecurity.blogspot.com/2015/10/simplifying-page-security-icon-in-chrome.html ) There are no plans, at the moment, to add a No Skateboarding sign to Chrome. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].