SHA1 sunset will block millions from encrypted net, Facebook warns
Companies unveil controversial fallback plan for tens of millions of browsers. — Tens of millions of Internet users will be cut off from encrypted webpages in the coming months unless sites are permitted to continue using SHA1 …
Context & Ripple Effects
Facebook set its own deadline months ago with a June announcement that it would stop accepting SHA-1 certificate signatures and require SHA-2, joining the industry-wide push to retire a hash function widely seen as cryptographically exhausted. But the transition has collided with a hard reality: tens of millions of people still browse on older devices and browsers that cannot verify SHA-2 certificates at all, an exposure flagged back in October and concentrated in the developing world, where old hardware dominates.
The friction is already visible: Mozilla was forced into temporarily reinstating SHA-1 support after Firefox users lost access to HTTPS sites. Facebook's warning and the companies' controversial fallback plan are the platform-side acknowledgment that a clean cutover would lock those users out of encrypted pages entirely.
First-order effects
- Site operators face an immediate fork: keep issuing SHA-1 certificates to preserve access for older browsers, or complete the SHA-2 migration and knowingly cut off a slice of their audience.
- Browser vendors feel the pressure first-hand — Mozilla has already reversed course once, reinstating SHA-1 support after Firefox users hit broken HTTPS connections.
Second-order effects
- The proposed fallback gives certificate authorities and large sites like Facebook a middle path, but it extends the life of a weakened hash function precisely where attackers have the most incentive, trading short-term access for lingering cryptographic risk.
- A messy, staggered SHA-1 retirement raises the coordination cost for the next deprecation: if each vendor handles cutoffs independently, breakage lands unevenly and forces more emergency reversals like Mozilla's.
Third-order effects
- If the pattern holds, cryptographic deprecation timelines will increasingly be shaped by global device-replacement lag rather than pure security math — a tension that resurfaces when Apple, Google, Microsoft, and Mozilla later announce a unified plan to retire TLS 1.0 and 1.1 together, suggesting the industry's answer is coordinated cutoffs plus fallbacks rather than unilateral deadlines.
The trend: Retiring weak cryptography is becoming a negotiation between security deadlines and the long tail of aging devices, pushing browser makers toward coordinated deprecations with compatibility fallbacks.