Revocation Checking Failures and Soft-Fail
What You'll Learn
You'll understand why browsers often accept certificates even when they can't verify if those certificates have been revoked—and why that's both practical and dangerous.
The Hard Reality of Revocation Checking
When your browser validates a certificate, it should check if that certificate has been revoked (using CRLs or OCSP, which you've already learned). But what happens if the revocation server is down, unreachable, or too slow?
Hard-Fail vs Soft-Fail
Hard-fail means: "If I can't check revocation status, reject the certificate." This is the secure approach—if you can't confirm a credential is valid, don't trust it.
Soft-fail means: "If I can't check revocation status, accept the certificate anyway." Most browsers use this approach by default.
Think of it like a nightclub bouncer checking IDs against a "banned list." Hard-fail means turning everyone away if the list isn't available. Soft-fail means letting everyone in when the list is down—including people who might actually be banned.
The Availability Attack Problem
Attackers can exploit soft-fail behavior by blocking your access to revocation services (OCSP responders or CRL distribution points). If they've stolen a certificate and know it's been revoked, they just need to prevent you from checking—then your browser will accept their compromised certificate due to soft-fail.
Why Soft-Fail Exists
Hard-fail sounds better, but revocation infrastructure is notoriously unreliable. If browsers enforced hard-fail, millions of legitimate websites would become unreachable whenever OCSP servers experienced downtime. It's a painful trade-off between security and availability.
Key Takeaway: Soft-fail revocation checking means browsers accept certificates when revocation status can't be verified—prioritizing availability over security and creating an exploitable vulnerability through availability attacks on revocation infrastructure.