Kind of... the HTTPS remote sites will have to pay to use competing brand of certs avoiding the expired ROOT LEVEL CERT in the operating system of the USER! Using updated version of this root cert will be of no use and is embedded deep into operating system.
Its a USER problem. Not a simple web server fix.
coding defects in SSL chain logic make these 2001 "almost immortal" root certs very problematic after sept 30 2021
https://scotthelme.co.uk/lets-encrypt-old-root-expiration/
Pandemonium :
https://news.ycombinator.com/item?id=28596317
if you read all the info this day you will see how this is a huge problem, especially for devices and os images that have been turned off dormant for 2 years, or incapable of kernel level OS updates.
Arrrrrrrrgh!!!! Idiocy.
My Solution!
Solution is never mentioned EVER, by any of these low IQ IT writers, but the trick I use is to disable all external clock updates, force time to BEFORE Sept 2021, and then connect to internet and patch or install signed patches... with clock set invalid. Every compiler ever made by apple had dead certs hidden in installers. Apple had to hack and revise over 12 years of compiler installer tools and slip them online this year for similar issue.
Android 7 ? fucked Android 6 ? fucked Android 5 ? fucked Older iOS? fucked everything in your house with little WiFi chips? fucked.
The Sky is Falling, and hundreds of millions of Pajeets and Africans will be crying Sept 30th 2021
Is it? Most systems will use self signed certificates because the web https system is broken. It is not hard to be your own certificate authority except for webpage certificate.
(post is archived)