Subj : Bug in the Let's Encrypt certificate authority code
To : Richard Menedetter
From : August Abolins
Date : Thu Mar 05 2020 07:36 pm
On 04/03/2020 12:37 p.m., Richard Menedetter : August Abolins wrote:
RM>The fix is easy and quick. Just renew the certificate as detailed
RM>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)