Skip to content

☑️ Check cert-manager certificates after "CAA Rechecking Incident"

License

Notifications You must be signed in to change notification settings

lunatic-cat/caaproblem-in-k8s

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 

Repository files navigation

CAA Problem in Kubernetes

What

Lets Encrypt will revoke ~3M certificates due a bug in domain validation. See more: CAA Rechecking Incident

This script helps to check if any of certificates created by cert-manager are affected.

Usage

./caaproblem-in-k8s.sh

will loop through all namespaces, find all certificates with kubectl, search through caa-rechecking-incident-affected-serials.txt.gz file with bad serial numbers:

Pass list of 'LANG=C sort'-ed bad serial nubers as first argument to skip download...
Doing: "curl ...caa-rechecking-incident-affected-serials.txt.gz..."
Getting all certificates from all namespaces, please be patient...
[  OK  ] ns1/secret-with-cert1 [domain1.com] serial=0300000b4e882e2268200dedf16d44eec861
[ FAIL ] ns2/secret-with-cert2 [domain2.com] serial=0300000b4e882e2268200dedf16d44eec864

Script doesn't change anything. Handle accordingly to force certificate regeneration

Requirements: curl, openssl

TODO

  • Automatically fix certificates(?)
  • Suggest to apply ingress with a different secretName to force regeneration

Also see

About

☑️ Check cert-manager certificates after "CAA Rechecking Incident"

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages