Re: Proposal: Marking HTTP As Non-Secure
[email protected] Thu, 28 Jan 2016 08:46:44 -0800 (PST)
| Newsgroups | gmane.comp.web.blink.devel,gmane.comp.web.chromium.security.devel,gmane.comp.mozilla.security |
|---|---|
| Message-ID | <[email protected]> |
> > On Monday, January 25, 2016 at 8:44:35 PM UTC+1, [email protected] > wrote: Hi all, what is the status of this proposal? It calls out for a deployment plan in 2015, but that did not materialize. What is the latest? Thanks! Regarding Chromium: """On Tuesday, during a presentation at the Usenix Enigma security conference in San Francisco, Google pushed the proposal out in the open with much more fanfare, and gave a sneak peek of how it’s going to look. (You can see the little red “x” on the padlock in the URL bar.)""" -- https://motherboard.vice.com/read/google-will-soon-shame-all-websites-that-are-unencrypted-chrome-https Then there is this bug tracking the implementation https://code.google.com/p/chromium/issues/detail?id=578317 -- 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].