Live data from Hacker News

CA Root expired on 30 May 2020

support.sectigo.com

11–20 of 154 posts

Re: CA Root expired on 30 May 2020

#11
post #5

This issue is largely cause by people still stuffing old root certificates in their certificate chains, and serving that to their users. As a general rule of thumb: 1) You don't need to add root certificates to your certificate chain 2) You especially don't need to add expired root certificates to the chain For additional context and the ability to check using `openssl` what certificates you should modify in your cha…

You shouldn't need to send the root certificate (unless the clients are _really_ dumb, but I worked with a lot of dumb clients, and did not see any issues with only sending intermediates and the entity cert), but a fair number of cert chain verifiers are fairly dumb and won't stop when they get to a root they know which makes things tricky.

If some of your clients don't have the UserTrust CA, but do have the AddTrust CA, up until today, you probably wanted to include the UserTrust CA cert signed by AddTrust. Clients with the UserTrust CA should see that the intermediate cert is signed by UserTrust and not even read that cross signed cert, but many do see the cross signed cert and then make the trust decision based on the AddTrust CA.

It's hard to identify clients in the TLS handshake to give them a cert chain tailored to their individual needs; there's some extensions for CA certs supported, but they're largely unused.

Re: CA Root expired on 30 May 2020

#12
post #6

DataDog failed this morning because of root CA issue.[0] Was a fun Saturday morning with 5000 alarms blowing up my phone. [0] https://status.datadoghq.com/incidents/6bqpd511nj4h

Yeah, took me a while to figure this out, the alerts were not welcome.

Found it ironic that the top of their page advertises "Security Monitoring now available".

Re: CA Root expired on 30 May 2020

#14

Any predictions how much the usage of CURLOPT_SSL_VERIFYPEER, false will increase in the next 7 days?

Yikes.. yeah, if you're going to do this, consider wrapping it in an `if (date < 2020-06-15)` and be sure to fix it properly before then. This reduces the ability to just forget about it (or have the fix constantly deprioritized) and leave your software with a security vulnerablty.

Re: CA Root expired on 30 May 2020

#15
This appears to have caused our Heroku managed apps to go offline for 70+ minutes.

https://status.heroku.com/incidents/2034

Anyone that was already connected was able to continue accessing the sites but new connections failed. This mostly affected web users.

Our main app server continued to crank along thankfully (also on Heroku) and that kept the mobile traffic going which is 90% of our users.

Edit: adding Heroku ticket link

Re: CA Root expired on 30 May 2020

#18
We had our CI systems fail today because of this. They were running Ubuntu 16.04. Check the below thread, they say an openssl bug is also a contributing factor. Removing the expired root CA fixed the issue for me. (edit: removed from the clients)

https://www.reddit.com/r/linux/comments/gshh70/sectigo_root_...

Re: CA Root expired on 30 May 2020

#20
Quick reminder from your friendly local SRE: never ever issue certificates that expire on weekends. Make certs expire in the middle of the afternoon on a business day wherever your operators live and work. The cert in question expires at May 30 10:48:38 2020 GMT, which smells suspiciously like a fixed time after the cert was generated, rather than at a well-chosen point in time.
Post reply on HN