Re: LetsEncrypt
By: Brian Rogers to All on Fri Oct 01 2021 06:28 pm
Anyone who had issues with certs signed by Let's Encrypt may have noticed issues. They had a maj
"oops" by not renewing their own certs which made
all other certs under them appear expired.
https://www.yahoo.com/news/internet-goes-down-millions-tech-021400230.html
I know on iPhones, email accounts that use servers who have certs signed
by Let's Encrypt have issues. I'm not an Apple person but if anyone knows how to force an update of the cert without having to recreate an email account I'd love to hear from you.
... Old bookkeepers never die, they just lose their figures.
Actually, for the sake of completition, what happened is that, before they were popular, Let's
Encrypt got their own certificate signed by a trusted CA (one of those which is trusted by most
Operating Systems). Let's Encrypt eventually became popular enough that their own certificate
became widely trusted with the years, but the old signature was kept in the trust chain for legacy
reasons.
When the certificate from the third party CA expired, old Operating Systems which:
* Don't have the Let's Encrypt now widely trusted certificate installed
* or do bogus certificate verification, because they try to verify Let's Encrypt's certificate
against the expired cert even if the Let's Encrypt one is stored as trusted
will fail to verify any legit Let's Encrypt cert.
It is unfortunate, but it is a problem with the SSL/TLS clients, really.
If your Operating System is not junk you may be able to remove the expired certificate from DST and
install the Let's Encrypt one. If you can't do that then I am afraid your Operating System is junk
and you should put it in /dev/null.
--
gopher://gopher.richardfalken.com/1/richardfalken
---
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL