Modern Revocation Alternatives
What you'll learn: How the industry is moving away from traditional CRLs and OCSP toward faster, more reliable revocation methods.
Traditional revocation mechanisms like CRLs and OCSP have serious limitations—they're slow, create privacy concerns, and often fail silently. The industry has developed several modern alternatives that address these weaknesses.
CRLSets and OneCRL
CRLSets (Chrome) and OneCRL (Firefox) are browser-maintained lists of revoked certificates. Instead of checking revocation status for every certificate in real-time, browsers bundle known-bad certificates directly into browser updates. Think of it like a "most wanted" list that travels with your browser rather than requiring a phone call to check each suspect.
These lists are:
- Small (only critical revocations)
- Fast (no network lookup)
- Always available (works offline)
The downside? They only include high-profile compromises, not every revoked certificate.
Short-Lived Certificates
Another approach is issuing certificates that expire quickly—sometimes in days or hours. If a certificate only lives for 3 days, you don't need complex revocation infrastructure. By the time you'd process a revocation, the certificate would already be expired naturally.
It's like a concert wristband that dissolves after the show instead of requiring a complex "banned attendee" database.
The Industry Shift
Major players are moving away from relying on OCSP and CRLs entirely. Let's Encrypt issues 90-day certificates specifically to reduce revocation dependency. Safari removed OCSP checking altogether. The focus has shifted to automation and short lifetimes rather than perfect revocation.
Key Takeaway: Modern revocation favors browser-curated blocklists (CRLSets/OneCRL) and short-lived certificates over traditional real-time checking, trading comprehensive coverage for reliability and performance.