Certificate Revocation Lists (CRLs)
You'll learn how CRLs distribute information about invalidated certificates and the practical challenges of this approach.
When a certificate needs to be revoked before its natural expiration (due to key compromise, CA error, or other reasons), someone needs to tell the world. A Certificate Revocation List (CRL) is basically a published blacklist of revoked certificates, signed by the CA that issued them.
CRL Structure
A CRL contains:
- Issuer information (which CA published this list)
- Issue and next update timestamps (when this CRL was published and when the next one is expected)
- List of revoked certificates with their serial numbers and revocation dates
- CA's digital signature to prevent tampering
Think of it like a "do not honor" list that credit card companies used to publish—except for certificates.
Distribution Points
CAs publish CRLs at CRL Distribution Points (CDPs), typically HTTP or LDAP URLs embedded in the certificate itself. Your software downloads the CRL from these locations before trusting a certificate.
Delta CRLs
A full CRL can become enormous. Delta CRLs only contain changes since the last full CRL—like incremental backups versus full backups—reducing download size and bandwidth.
Caching Strategies
Because downloading a CRL for every validation is slow, clients cache them. However, this creates a window where recently-revoked certificates still appear valid until the cache expires.
Scalability Limitations
Here's where CRLs struggle:
- Size: Large CAs may revoke thousands of certificates—the list grows constantly
- Download overhead: Every client must fetch megabytes of data
- Freshness vs performance tradeoff: Cache too long, and revocations are delayed; cache too short, and performance suffers
- Offline validation: If you can't reach the CDP, do you fail open (security risk) or closed (availability risk)?
Key Takeaway: CRLs provide a straightforward revocation mechanism by publishing signed blacklists, but their scalability limitations—massive file sizes, bandwidth requirements, and caching tradeoffs—make them impractical for modern high-volume certificate ecosystems.