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

Revocation Reason Should be Requested #9880

Open
BenWilson-Mozilla opened this issue Jan 23, 2024 · 1 comment
Open

Revocation Reason Should be Requested #9880

BenWilson-Mozilla opened this issue Jan 23, 2024 · 1 comment

Comments

@BenWilson-Mozilla
Copy link

Shouldn't Certbot request a reason code (especially for Key Compromise) before submitting a revocation request? My understanding is that default behavior doesn't ask whether the revocation is for key compromise or other reasons. That information should be passed on to the Let's Encrypt CRL.

@osirisinferi
Copy link
Collaborator

osirisinferi commented Jan 23, 2024

My understanding is that default behavior doesn't ask whether the revocation is for key compromise or other reasons.

Correct, the default reason is unspecified.

That information should be passed on to the Let's Encrypt CRL.

Users can use the --reason option to e.g. specify --reason keycompromise in combination with the revoke subcommand.

Note that Certbot currently is not affiliated any longer with Let's Encrypt, but is developed by the EFF 🙂

Is your request that Certbot should always ask for a reason, if not provided by the user on the CLI?

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

No branches or pull requests

2 participants