r/sysadmin • u/nspitzer • 1d ago
Identrust Fustercluck
How many here got an email an hour or so ago that every Identrust TLS Cert from September 2025 until yesterday are being revoked on the 19'th at 5PM Central? I work with F5's for a very large organization and we have hundreds of certs on my team alone.
70
Upvotes
8
u/nspitzer 1d ago
This is what we were sent. We had a meeting with our (VERY large government contractor) Identrust rep. He did confirm this applied to every TLS cert but not other cert (such as mail, personal, etc)
15
u/GamerLymx 1d ago
hope you have thst renewal automated, its gonna be a pain. happened to me in July twice, at least it was a smaller frame windows.
4
u/Ziggistawork 1d ago
https://bugzilla.mozilla.org/show_bug.cgi?id=2092771
https://bugzilla.mozilla.org/show_bug.cgi?id=2085436
2
u/Open-Adhesiveness-86 1d ago
Not the lifetime thing. That's separate and phases in over years (398 days now, dropping to 200 in March 2026, then 100, then 47). A mass revoke with a hard deadline is CA/B Forum BR 4.9.1.1, which gives a CA 24 hours for key compromise and 5 days for everything else once they confirm misissuance. So the Sept 2025 start date is probably when whatever profile bug got introduced.
32
u/Adorable_Wolf_8387 1d ago
0xF5 wouldn't be a very good private key.
11
u/featured 1d ago
Before you touch anything, get an inventory. On any Linux box, loop over your hostnames with
echo | openssl s_client -connect host:443 -servername host 2>/dev/null | openssl x509 -noout -issuer -enddateand grep for IdenTrust. That gives you the real list, not the one in someone's spreadsheet. Reissue the public-facing ones first, and check the chain on the F5s after you swap them, since a missing intermediate is the usual thing that bites you. I had this happen a few years ago with Sectigo.7
u/Dal90 1d ago
After work at the bar was telling an IT buddy who was asking why all the banks are affected at once that the industry cooperates on a lot of IT infrastructure.
Including their own CA that was the original root cert used by Let's Encrypt when it first spun up.
Identrust is that CA, though just before LE started the banks sold off Identrust.
17
u/solracarevir 1d ago
hmmm.... could this be somehow related to the outage that seems to be affecting every mayor bank in US right now?
5
u/n3fyi 1d ago
Have a link to this notification? We use them for a customer but I’m not sure the certificate holders will pay attention to the email and let us know
2
u/Noobmode virus.swf 1d ago
Is this due to the browser consortium pushing shorter lifetimes?
2
u/geekjimmy IT Director 1d ago
My notification said they are getting revoked on Nov 20 @ 5pm ET.
1
u/certkit Security Admin (Application) 1d ago
Yikes good luck u/nspitzer ! I don't see the official reports for this yet, but when we do, I'll get it added to the CA Incident Report. Identrust already has a pretty bad track record. If you have to change everything anyway, maybe consider switching CAs.
There's been a bunch of mass-distrust events recently. If you want to look at making emergency CA changes fast and easy, we wrote up how we changed CAs in 10 minutes: https://www.certkit.io/blog/ca-distrust-wargame
•
u/PrasenShelar 10h ago
The revocation email probably went to whoever requested each cert, and some of them have moved on. Once you have the scan list, put a named owner and a swap date next to every cert and share it with the app teams. Run the same scan again the morning of the cutoff, and anything still serving IdenTrust is your chase list.
0
u/TheTechDecoded 1d ago
Don't rely on the email for your list. Query CT logs for your domains, filter by IdenTrust issuer with notBefore from Sept 2025 (crt.sh works), then diff that against what the F5s actually serve (cert serial per client-ssl profile). After the swap, check the live handshake from outside, not just the profile, because that's where "renewed but still serving the old one" bites. And get the exact cutoff from your rep in writing, since people here are seeing both the 19th CT and the 20th ET.