This repository contains the source code for Certgrinder, including docs. Read more on ReadTheDocs: https://certgrinder.readthedocs.io/en/latest/
Certgrinder is a client/server system written in Python to handle Letsencrypt certificate issuing on a central host (the Certgrinder server), rather than on the machines which need the certificates (the Certgrinder clients). This is accomplished by redirecting the LetsEncrypt challenges to the Certgrinder server. For
DNS-01 challenges this is done with a
CNAME record and for
HTTP-01 challenges it is done with a
HTTP 301 redirect.
To get a certificate the Certgrinder client calls the Certgrinder server (typically over
SSH) with a
stdin and (if all goes well) get a signed certificate in return on
Certgrinder support both
ECDSA keys and certificates, and defaults to getting both kinds.
Read more on ReadTheDocs: https://certgrinder.readthedocs.io/en/latest/
There is a Docker image for the client at https://hub.docker.com/r/certgrinder/certgrinder
The approach with a central host serving all challenges simplifies getting certificates for stuff like loadbalanced or anycast services, where it can be impossible to predict which cluster node the LetsEncrypt challenge checker will hit when using
DNS-01with a separate delegated zone dedicated to serve the challenges is safer than opening up dynamic updates of your primary zone(s) with your provider.
Migrating services to new infrastructure becomes simpler because the new infrastructure can get real certificates before changing DNS to point to the new infrastructure.
Certgrinder makes it trivial to get certificates for infrastructure behind firewalls or even on networks with no Internet connection. As long as the Certgrinder client can reach the Certgrinder server it is possible to use
DNS-01to issue certificates for the client.
Certgrinder does not rotate the RSA/ECDSA keypair on each certificate renewal, which makes
TLSAand similar public key pinning easy. The Certgrinder client can output and check such
SPKIpins for the keypairs it manages, as well as checking correctness of
TLSArecords in the DNS.
Certgrinder supports fetching OCSP responses via the Certgrinder server. Having Certgrinder fetch the OCSP response makes it possible to configure OCSP stapling without relying on the various TLS servers own OCSP-fetching implementation. It also means that OCSP stapling can be done on servers behind strict firewalls or with no Internet connection, as the communication with CA is done via the Certgrinder server.
Certgrinder supports alternate chain selection and understands the longer chain used by LetsEncrypt since May 2021.
The central host with the LetsEncrypt signing stack is called the "Certgrinder server". The individual servers (the ones that need the certificates) are called "Certgrinder clients". These match the two Python packages