-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support to regen realm private keys on specified intervals #89
Comments
I see an issue with this - at the moment the hosts themselves execute the |
Right. I would not really depend on that. Maybe older private keys could be saved in the CA directory which still has a valid cert using this key. |
For the common deployments using DebOps, e. g. VPSes or so using LE, key regeneration should be the default. I suspect that internal CAs or external CAs are used very infrequently for such deployments. For such cases we could recommend in the docs to disable |
Currently, the realm key used for all certificates of this realm (internal, external, ACME) is created on realm creation. In the case of ACME and LE, the certificate is renewed at least all 3 months. Other certs are rotated less frequently. It should be possible to specify the wanted private key renewal period which can happen at cert renewal.
Ref: https://letsencrypt.org/2015/11/09/why-90-days.html
The text was updated successfully, but these errors were encountered: