Category: 

What is a Certificate Revocation List?

Article Details
  • Written By: S.A. Keel
  • Edited By: Angela B.
  • Last Modified Date: 21 September 2016
  • Copyright Protected:
    2003-2016
    Conjecture Corporation
  • Print this Article
Free Widgets for your Site/Blog
The atmosphere of Jupiter's moon Io collapses every time it is eclipsed by the planet.   more...

September 29 ,  2008 :  The Dow Jones Industrial Average experienced its largest one-day drop in history.  more...

A certificate revocation list (CRL) is a component of the International Telecommunication Union's (ITU) X.509 security standard. According to the X.509 standard, a certificate authority (CA) can use a CRL to either place a hold on, or explicitly revoke, any digital security certificate that it has issued and which has not expired. The CRL is then distributed and used by various computer programs to confirm the validity of the security certificates used to identity a source.

The generation of a security certificate by a CA falls under what's called a public key infrastructure (PKI). Through a PKI, any user can be identified by the public key of their security key pair, the user's private key being the other half of the pair. A user then contacts a CA and, using his public key as identification, requests a security certificate. After some measure of vetting the user's actual identity, the CA can then issue a certificate that is bound to the user's public key. By this method, the CA acts as a trusted third party, guaranteeing the identity of the user who's been issued a certificate.

Ad

A digital security certificate is typically given a one- or two-year lifespan. After the certificate expires, the user needs to renew his existing certificate by re-validating his identity or by requesting a new certificate outright. The expiration date of a certificate is included in the certificate itself, so computer software knows when to no longer honor an expired certificate. There are times, however, when a certificate may need to be revoked before its expiration date. For those instances, a CA must maintain a certificate revocation list that lists any certificates that have not expired but cannot be trusted for some reason.

A certificate revocation list contains a number of possible reasons for revoking a certificate. The most common being that the private key for the owner of the certificate is no longer safe, at which point the certificate remains on the listing until its expiration date. In this case, the user must generate a new key pair and request an entirely new certificate.

There are, of course, other reasons a certificate may appear in the CRL. A certificate can be listed if it has been superseded by another or there is some change to the information contained in the certificate about its owner, or if the CA itself has been compromised, whereupon the CA itself will appear on what's called an authority revocation list (ARL). Another reason a certificate may appear on a CRL is because the certificate is being placed on hold for some reason. In the case of a certificate listed as being held, it can then be reinstated in the next CRL distributed by the CA. The many, frequent changes to the statuses of digital security certificates mean a certificate revocation list usually has a life expectancy of about 24 hours, though sometimes less.

Ad

You might also Like

Recommended

Discuss this Article

Post your comments

exception 'Exception' with message 'error writing captcha: Duplicate entry '2147483647' for key 'PRIMARY'' in /ssd/www/wisegeek/public_html/_core/classes/public/Captcha.php:44
Stack trace:
#0 /ssd/www/wisegeek/public_html/_core/controls/public/ControlDiscussionPostBox.php(324): Captcha->createCaptcha()
#1 /ssd/www/wisegeek/public_html/framework/classes/Control.php(104): ControlDiscussionPostBox->preRender(false)
#2 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): Control->render()
#3 /ssd/www/wisegeek/public_html/tpl/default-nocustom-lu/pages/public/article/article.htm(526): Control->__toString()
#4 /ssd/www/wisegeek/public_html/framework/classes/Control.php(300): require('/ssd/www/wisege...')
#5 /ssd/www/wisegeek/public_html/framework/classes/Control.php(309): Control->requireTpl('pages/public/ar...', Object(PageArticleCom), true)
#6 /ssd/www/wisegeek/public_html/framework/classes/Control.php(131): Control->renderTpl('pages/public/ar...', Object(PageArticleCom))
#7 /ssd/www/wisegeek/public_html/framework/classes/FormDataControl.php(87): Control->renderTemplate()
#8 /ssd/www/wisegeek/public_html/framework/classes/Control.php(109): FormDataControl->renderTemplate()
#9 /ssd/www/wisegeek/public_html/framework/classes/ScriptPage.php(50): Control->render(false)
#10 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): ScriptPage->render()
#11 /ssd/www/wisegeek/public_html/framework/classes/Page.php(97): Control->__toString()
#12 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(443): Page->processRequest()
#13 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(7): PublicFrontController->renderPage()
#14 /ssd/www/wisegeek/public_html/index.php(11): PublicFrontController::run()
#15 {main}