Let’s Encrypt Discovers CAA Bug, Must Revoke Customer Certificates

    0
    33

    rufey writes: The free SSL certificate provider Let’s Encrypt is going to revoke 2.6% of the SSL certs issued by them that are currently active, due to a bug in boulder, the Certificate Authority Authorization (CAA) software Let’s Encrypt uses. Ars Technica reports: “Let’s Encrypt uses Certificate Authority software called Boulder. Typically, a Web server that services many separate domain names and uses Let’s Encrypt to secure them receives a single LE certificate that covers all domain names used by the server rather than a separate cert for each individual domain. The bug LE discovered is that, rather than checking each domain name separately for valid CAA records authorizing that domain to be renewed by that server, Boulder would check a single one of the domains on that server n times (where n is the number of LE-serviced domains on that server). Let’s Encrypt typically considers domain validation results good for 30 days from the time of validation — but CAA records specifically must be checked no more than eight hours prior to certificate issuance. The upshot is that a 30-day window is presented in which certificates might be issued to a particular Web server by Let’s Encrypt despite the presence of CAA records in DNS that would prohibit that issuance. Since Let’s Encrypt finds itself in the unenviable position of possibly having issued certificates that it should not have, it is revoking all current certificates that might not have had proper CAA record checking on Wednesday, March 4. Users whose certificates are scheduled to be revoked will need to manually force-renewal before then. If an admin does not perform this manual renewal step, browsers reaching their websites will show TLS security warnings due to the revoked certificates. Let’s Encrypt certificates are issued for 90-day intervals, and Certbot automatically renews them only when 30 days or less are left on the cert — so this could mean roughly two months of browser errors if the manual forced renewal isn’t performed.” The CAB Forum, which oversees the public CAA space, has a ticket for this specific issue. According to a community post on Let’s Encrypt’s website, 3,048,289 of the ~116 million overall active Let’s Encrypt certificates are affected. Read more of this story at Slashdot.

    LEAVE A REPLY

    Please enter your comment!
    Please enter your name here