Originally created by @basbebe on GitHub (Feb 10, 2016).
It would be great to have an option for creating a separate key for every domain in use.
It would also be nice if it would be possible to create some entropy before regenerating keys, just like calomel does: https://calomel.org/lets_encrypt_client.html
Originally created by @basbebe on GitHub (Feb 10, 2016).
It would be great to have an option for creating a separate key for every domain in use.
It would also be nice if it would be possible to create some entropy before regenerating keys, just like calomel does:
https://calomel.org/lets_encrypt_client.html
Certificate keys are per certificate, the only shared part is the account key.
Generating entropy shouldn't be the job of this script, if you are running low on entropy you should run haveged or configure some other way of generating entropy.
@lukas2511 commented on GitHub (Feb 10, 2016):
Certificate keys are per certificate, the only shared part is the account key.
Generating entropy shouldn't be the job of this script, if you are running low on entropy you should run haveged or configure some other way of generating entropy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @basbebe on GitHub (Feb 10, 2016).
It would be great to have an option for creating a separate key for every domain in use.
It would also be nice if it would be possible to create some entropy before regenerating keys, just like calomel does:
https://calomel.org/lets_encrypt_client.html
@lukas2511 commented on GitHub (Feb 10, 2016):
Certificate keys are per certificate, the only shared part is the account key.
Generating entropy shouldn't be the job of this script, if you are running low on entropy you should run haveged or configure some other way of generating entropy.