4 ms·
This change will only add the grey 'not secure' text to the address bar and not hinder functionality. So it is just less green and not more red as with invalid
by aequitas 8y ago
This change will only add the grey 'not secure' text to the address bar and not hinder functionality. So it is just less green and not more red as with invalid or self-signed certificates where you have to perform additional steps to continue.
- jessaustin 8y agoThat's in this version. How many versions until we get the ridiculous harassment already required for self-signed certs?
- sp332 8y agoThe older blogpost that laid out the roadmap stops here. https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html https://security.googleblog.com/2016/09/moving-towards-more-... It's not impossible that they would do that in the future, but their plans so far don't seem to include that.
- zokier 8y agoThere are already https only features, and their number will probably just keep increasing https://www.digicert.com/blog/https-only-features-in-browsers/ https://www.digicert.com/blog/https-only-features-in-browser... https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins https://www.chromium.org/Home/chromium-security/deprecating-... https://blog.mozilla.org/security/2018/01/15/secure-contexts-everywhere/ https://blog.mozilla.org/security/2018/01/15/secure-contexts...
- aequitas 8y agoI can only agree with that. Having security contexts as a formal concept and requiring secure transport for certain features. Stuff like webcam or other hardware access (bluetooth) should really not be allowed from a insecure (MITM'ed?) source.
- bcheung 8y agoFor now.. Look at the trend. First it was just a small SEO bump.