"Breaking" the browser for a large number of users will only lead to one thing: Users switching to a browser that still supports SHA-1 certs issued after Jan 1s

"Breaking" the browser for a large number of users will only lead to one thing: Users switching to a browser that still supports SHA-1 certs issued after Jan 1st, 2016. No privacy improvement there either. Additionally, there are many valid use-cases for replacing certificates, e.g. corporate proxies. They should just stop using outdated hashing algorithms for those certs. It's not Mozilla's place to decide whether that use-case is valid or not. SHA-1 was never fully disabled; it's just that certificates using SHA-1 issued after that date weren't accepted anymore. Telemetry is important to understand the ramifications of this issue. This change is likely to be reverted once Mozilla understands the implications. Take a look at the discussion on Mozilla's mailing list for more insight into their thinking[1]. [1]: https://groups.google.com/forum/#!topic/mozilla.dev.platform/ZNKxYgIk_Sg https://groups.google.com/forum/#!topic/mozilla.dev.platform...