Hacker News
- Marking HTTP as Non-Secure https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure 231 comments
- Chrome 56 will mark HTTP pages with password fields as non-secure https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html?m=1 398 comments
Lobsters
- Chromium Considers Marking HTTP As Non-Secure https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure 9 comments browsers , security , web
- Marking HTTP As Non-Secure https://www.chromium.org/home/chromium-security/marking-http-as-non-secure 21 comments netsec
- Chrome 56 will mark HTTP sites that transmit passwords or credit cards as non-secure https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html 109 comments webdev
- Chrome Security Team Considers Marking All HTTP Pages As 'Non-Secure' https://www.techdirt.com/articles/20141213/07112629425/chrome-security-team-considers-marking-all-http-pages-as-non-secure.shtml 13 comments technology
- [PSA] From the end of January with Chrome 56, Chrome will mark HTTP sites that collect passwords or credit cards as non-secure. https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html 36 comments webdev
- Chrome has not explicitly labelled HTTP connections as non-secure. Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure. https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html 4 comments chrome