Skip to content
Discussion options

You must be logged in to vote

Good news: that is already what CertMate does. There is nothing to configure — every renewal generates a fresh private key.

The reason is certbot's own default. From certbot --help all:

--reuse-key    When renewing, use the same private key as the existing
               certificate. (default: False)
--no-reuse-key ... Not reusing private keys is the default behavior of Certbot.

CertMate never passes --reuse-key on any code path, so the default stands: each renewal produces a new keypair, and the old key is retired with the old certificate.

Verifying it on your instance

Compare the public-key fingerprint before and after a renewal — it will differ:

openssl pkey -in privkey.pem -pubout -o…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@Peter-A-Tech
Comment options

@fabriziosalmi
Comment options

Answer selected by fabriziosalmi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants