Bug in the Let's Encrypt certificate authority code

"Let's Encrypt were in the news a few days ago when they announced they
had issued a billion certificates. Yesterday they broke the news that
they're forced to revoke 2.6% of active Let’s Encrypt TLS/SSL
certificates due to the 2020.02.29 CAA Rechecking Bug. They're in the
process of notifying some users that their certificates will be revoked
today, March 4th 2020. Check the thread for more details and to see if
you're affected."


https://tinyurl.com/r7esfu5

--- TB68.4.1/Win7
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Hi August!

04 Mar 2020 19:01, from August Abolins -> All:

Bug in the Let's Encrypt certificate authority code

The fix is easy and quick.
Just renew the certificate as detailed in their mail.
takes less than 30 seconds.

CU, Ricsi

... Wise man see more from the bottom of a well than fools from a mountain.
--- GoldED+/LNX
* Origin: Is anyone here an investigative reporter? (2:310/31)

On 04/03/2020 12:37 p.m., Richard Menedetter : August Abolins wrote:

The fix is easy and quick. Just renew the certificate as detailed
in their mail. takes less than 30 seconds.

The article makes it sound that the billion affected certificates and the revocation process is "critical" due to the volume. :( Shameful reporting of the original announcement.

If "renewing" is all that is required, then the revocation announcement seems to
be overblown indeed.

So, does "renewing" provide you with a different certificate and the processing automatically revokes the old one in one simple step?

I only posted the news when I remembered that someone in FTN-world mentioned they were using Let's Encrypt.


--
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc

--- TB68.4.1/Win7
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)