diff options
| author | alexzorin <alex@zorin.id.au> | 2022-04-01 23:27:11 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-01 23:27:11 +0300 |
| commit | d45a702649cd2241d61475e9746f41d5e7ab39e5 (patch) | |
| tree | bdcbf0874be21560cf7271585cf6205fe7c8c7eb | |
| parent | fe0b637e4d5acf3d24ba0d5e3feca440c2a32717 (diff) | |
changelog: clarify --new-key entry (#9259)
@osirisinferi pointed out [in chat](https://opensource.eff.org/eff-open-source/pl/y5whp5ny378wuedi8gd7995qbo) that the way this entry was written, suggested that `--new-key` might affect whether `--reuse-key` is set or not.
I think the second sentence was the main culprit, so I've nixed it and replaced it with a reminder about our other flags.
This maybe calls out more for a documentation section but let's fix this quickly before the release.
| -rw-r--r-- | certbot/CHANGELOG.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/certbot/CHANGELOG.md b/certbot/CHANGELOG.md index 6a6d39af0..6d87d9f67 100644 --- a/certbot/CHANGELOG.md +++ b/certbot/CHANGELOG.md @@ -7,9 +7,10 @@ Certbot adheres to [Semantic Versioning](https://semver.org/). ### Added * Added `--new-key`. When renewing or replacing a certificate that has `--reuse-key` - set, it will force a new private key to be generated. - Combining `--reuse-key` and `--new-key` will replace the certificate's private key - and then reuse it for future renewals. + set, it will force a new private key to be generated, one time. + + As before, `--reuse-key` and `--no-reuse-key` can be used to enable and disable key + reuse. ### Changed |