3 ms·
We scan our codebase for anything that looks like a cert and send emails when it gets close. Might not have helped here if it was an intermediate owned by a CA.
by wbl 8y ago
We scan our codebase for anything that looks like a cert and send emails when it gets close. Might not have helped here if it was an intermediate owned by a CA. There but for the grace of God go I.
- adtac 8y agoWhy do you have certificates in your code to begin with?
- justinclift 8y agoIf you have your own CA for whatever reason, it's common to distribute the root and intermediate certs with your code so things can resolve. You don't ship the signing keys with the certs, as that would be bad. ;)
- justinclift 8y agos/resolve/validate/
- lvh 8y agoIf you want to get rid of those and they're public certs: odds are they're in Certificate Transparency logs and you can monitor them from there.
- tialaramex 8y agoMonitoring CT lets you verify that somebody renewed the certificate, but it doesn't verify they actually installed the replacement correctly. My employer (Kynd.io) currently monitors public web sites for customers so we can flag e.g. "Hey this site cert expires in a week! If it's dead probably just switch it off, otherwise renew the certificate" and we're in the process of integrating CT but mostly so we can say "You already have a newer cert but need to go install it" in our How To Fix instructions.