|
No surprise there. It's heading toward 47 days in 2029
1. As of March 15, 2026, the maximum lifetime for a TLS
certificate will be 200 days.
2. As of March 15, 2027, the maximum lifetime for a TLS
certificate will be 100 days.
3. As of March 15, 2029, the maximum lifetime for a TLS
certificate will be 47 days.
Been using LetsEncrypt for many years with a 90 day lifetime and
automated it with DCM for LetsEncrypt (https://ledcm.valadd.com/) which
I have *just* about finished for release as an open source project (just
working on documentation at this point). Maybe IBM would be interested....
Pete Helgren
www.petesworkshop.com
CISSP - MSCM
GIAC Cloud Penetration Tester
AWS Certified Cloud Practitioner
Microsoft Certified: Azure Fundamentals
On 3/17/2026 5:14 PM, Jack Woehr via MIDRANGE-L wrote:
TLS Certificate Lifetime Now 200 Dayshttps://www.helpnetsecurity.com/2026/03/16/globalsign-tls-certificate-lifecycle-management
https://www.linkedin.com/company/procern-technology-solutions/>
Jack Woehr
Independent Consulting Programmer
[icon] 303-847-8442<tel:303-847-8442>
[icon] jack.woehr@xxxxxxxxxxx<mailto:jack.woehr@xxxxxxxxxxx>
[icon] www.procern.com<https://www.procern.com>
[icon] Stay Connected!<
https://procern.com/24-7-monitoring-itil-management/>
[photo]
Upgrade your IT state of mind!<
attachments is for the intended recipient(s) only and may contain
NON-DISCLOSURE NOTICE: This communication including any and all
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
jack.woehr@xxxxxxxxxxx www.procern.com Stay Connected!Upgrade your IT
[__tpx__]
Jack WoehrIndependent Consulting Programmer 303-847-8442
state of mind!NON-DISCLOSURE NOTICE: This communication including any and
all attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.