When a client performs Certificate revocation checking it's my understanding the CRL is cached in the CryptoAPI cache. Is this cache a memory cache or disk cache? Meaning, does the client cache the CRL for the validity period regardless of a reboot or upon each reboot the CryptoAPI cache is purged and the client re-downloads the CRL? Thanks, PaulT15

This is indeed a great download! A must-read! If you want details about CRLs and caches in particular, you could also reach out to http://windoh.wordpress.com/2011/04/23/crl-caching-in-windows-and-a-little-bit-about-ocsp-caching-too/ I've written this blog post more than a year ago, but I guess it's still valuable enough for most people. Ciao!