An informal talk about how CloudFlare helps CILogon and NCSA distribute CRLs.
Presented at the 21st TAGPMA Face-to-Face Meeting, Pittsburgh, PA, U.S.A. May 27-29 2015.
DNS control for that domain to CloudFlare • Configure source URLs in CloudFlare (e.g., crl.cilogon.org / crl.ncsa.illinois.edu) • Set custom caching for *.crl and *.r0 files (see next slide) • Register new CRL URLs with IGTF $ cat cilogon-basic.crl_url http://crl-cilogon.ncsa-security.net/cilogon-basic.crl http://crl.cilogon.org/cilogon-basic.crl $ cat NCSA-tfca-2013.crl_url http://crl-ncsa.ncsa-security.net/tfca2013.crl http://crl.ncsa.illinois.edu/tfca2013.crl
file • fetch-crl will not install CRL with invalid signature • In case of CloudFlare outage • fetch-crl will use secondary CRL URL (e.g., crl.cilogon.org / crl.ncsa.illinois.edu) • Synchronization • fetch-crl: Attempt to install example.r0 failed since the current CRL is more recent than the one that was downloaded. • So far so good? Anyone seen problems with our CRLs lately? • In case of problems, we can update ncsa-security.net to point back to NCSA instead of CloudFlare