Introduce 'revoke-renewed' #547
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When easyrsa "renews" a certificate, the current certificate is moved to a sub-directory for renewed certificates and renamed to the serial number of the certificate. This makes it difficult to subsequently revoke the old certificate. The new behaviour is for easyrsa to move the certificate without renaming the file. This means the certificate can be revoked by name. Once a renewed certificate is revoked, it is moved to the 'revoked' sub-directory, along with all other revoked certificates. The same mechanism also manages keys, requests, PKCS and inline files. Behaviour summary: * revoke moves certificates to 'revoked' - Unchanged Rename the certificate to its serial number - Unchanged * renew moves certificates to 'renewed' - Unchanged renew does not rename the certificate to its serial number - Changed Important: Only one certificate of a specific name (eg. john) can be renewed at the same time. To renew another certificate called 'john' the first MUST be revoked. * revoke-renewed: takes the certificate from 'renewed' - Changed moves the certifiate to 'revoked' - Changed renames the certificate to its serial number - Unchanged * All revoked certificates are moved to the 'revoked' sub-directory. Signed-off-by: Richard T Bonhomme <tincantech@protonmail.com>
TinCanTech
added
Full-Approval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When easyrsa "renews" a certificate, the current certificate is moved
to a sub-directory for renewed certificates and renamed to the serial
number of the certificate.
This makes it difficult to subsequently revoke the old certificate.
The new behaviour is for easyrsa to move the certificate without
renaming the file. This means the certificate can be revoked by name.
Once a renewed certificate is revoked, it is moved to the 'revoked'
sub-directory, along with all other revoked certificates.
The same mechanism also manages keys, requests, PKCS and inline files.
Behaviour summary:
revoke moves certificates to 'revoked' - Unchanged
Rename the certificate to its serial number - Unchanged
renew moves certificates to 'renewed' - Unchanged
renew does not rename the certificate to its serial number - Changed
Important:
Only one certificate of a specific name (eg. john) can be renewed
at the same time.
To renew another certificate called 'john' the first MUST be revoked.
revoke-renewed:
takes the certificate from 'renewed' - Changed
moves the certifiate to 'revoked' - Changed
renames the certificate to its serial number - Unchanged
All revoked certificates are moved to the 'revoked' sub-directory.
Signed-off-by: Richard T Bonhomme tincantech@protonmail.com