[GH-ISSUE #8] Revoke certificate #7

Open
opened 2026-02-26 21:31:05 +03:00 by kerem · 4 comments
Owner

Originally created by @beppler on GitHub (Jan 30, 2018).
Original GitHub issue: https://github.com/ridercz/AutoACME/issues/8

Originally assigned to: @ridercz on GitHub.

It would be awesome if there are a option to revoke certificates com the cli.

It should operate like delhost, but run the certificate revoke before delete files.

Originally created by @beppler on GitHub (Jan 30, 2018). Original GitHub issue: https://github.com/ridercz/AutoACME/issues/8 Originally assigned to: @ridercz on GitHub. It would be awesome if there are a option to revoke certificates com the cli. It should operate like delhost, but run the certificate revoke before delete files.
Author
Owner

@ridercz commented on GitHub (Jan 30, 2018):

Good idea, I'll implement this once I have some free time.

<!-- gh-comment-id:361749144 --> @ridercz commented on GitHub (Jan 30, 2018): Good idea, I'll implement this once I have some free time.
Author
Owner

@Timo-Breumelhof commented on GitHub (Jul 17, 2020):

This would be really cools, as now we get expiry emails for domain names the are not on our server any more :-)

<!-- gh-comment-id:660006424 --> @Timo-Breumelhof commented on GitHub (Jul 17, 2020): This would be really cools, as now we get expiry emails for domain names the are not on our server any more :-)
Author
Owner

@avonwyss commented on GitHub (Jul 17, 2020):

Revoking as CLI operation would be good, but...
Does this indeed prevent the expiry email from being sent? I had previously re-issued new certs for domains and still got expiry mails for the then obsolete certs. My understanding is that revoking is used when a certificate/provate key have been compromised, it does not necessarily mean that the cert shouldn't be renewed with a new private key...
https://letsencrypt.org/docs/revoking/
https://community.letsencrypt.org/t/do-you-have-to-revoke-previous-certificates-if-you-want-to-generate-a-new-one/127473

<!-- gh-comment-id:660036034 --> @avonwyss commented on GitHub (Jul 17, 2020): Revoking as CLI operation would be good, but... Does this indeed prevent the expiry email from being sent? I had previously re-issued new certs for domains and still got expiry mails for the then obsolete certs. My understanding is that revoking is used when a certificate/provate key have been compromised, it does not necessarily mean that the cert shouldn't be renewed with a new private key... https://letsencrypt.org/docs/revoking/ https://community.letsencrypt.org/t/do-you-have-to-revoke-previous-certificates-if-you-want-to-generate-a-new-one/127473
Author
Owner

@Timo-Breumelhof commented on GitHub (Jul 17, 2020):

oh ok, thanks for the feedback :-)

<!-- gh-comment-id:660052715 --> @Timo-Breumelhof commented on GitHub (Jul 17, 2020): oh ok, thanks for the feedback :-)
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AutoACME#7
No description provided.