4 ms·
For anyone wondering exactly what the current plan is regarding these secure/not-secure indicators in upcoming releases, the Chromium Project has a detailed pro
by niel 8y ago
For anyone wondering exactly what the current plan is regarding these secure/not-secure indicators in upcoming releases, the Chromium Project has a detailed proposal and timeline: https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure https://www.chromium.org/Home/chromium-security/marking-http...
Basically it comes down to eventually removing "secure" indicators completely and only indicating when a page is considered "not secure".
As an aside, Let's Encrypt has been a godsend to me during this change.
- tmikaeld 8y ago"Let's Encrypt has been a godsend to me during this change." I think that's what made Google push this, since they are on the board of advisors for the Let's encrypt certificate authority.
- nsgi 8y agoIt's more likely that Google's support for HTTPS everywhere caused them to do both. It introduced HTTPS as a ranking signal in 2014, well before Let's Encrypt.