&quot;Breaking&quot; 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&#x27;s not Mozilla&#x27;s place to decide whether that use-case is valid or not.<p>SHA-1 was never fully disabled; it&#x27;s just that certificates using SHA-1 issued after that date weren&#x27;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&#x27;s mailing list for more insight into their thinking[1].<p>[1]: <a href="https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!topic&#x2F;mozilla.dev.platform&#x2F;ZNKxYgIk_Sg" rel="nofollow">https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!topic&#x2F;mozilla.dev.platform...</a>