Skip to content
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 for CSRs so private keys are not stored on the certwarden CVS? #61

Open
clas0415 opened this issue Sep 16, 2024 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@clas0415
Copy link

Would CSRs be a possibility?

AFAIK this is possible with some other ACME clients/methods: https://community.letsencrypt.org/t/is-there-a-way-i-can-just-provide-a-csr-and-get-a-cert-manually/85422

My reasoning is that, by storing all the private keys for servers, then the certwarden server becomes quite a target.
But if the servers generate keys locally and pass only the CSR to certwarden, then it could reduce the single point of risk.

@clas0415 clas0415 changed the title Support for CSRs so keys are stored on the certwarden CVS? Support for CSRs so private keys are not stored on the certwarden CVS? Sep 16, 2024
@gregtwallace gregtwallace added the enhancement New feature or request label Sep 16, 2024
@gregtwallace
Copy link
Owner

This is an interesting idea. I'd need to ponder if I can make this work without too much extra development.

That said, from a security standpoint, the account keys would still live in cert warden so there would still be a pretty significant compromise of your domains if the keys were stolen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants