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

more clarity around delegation revocation for non-STAR certs #144

Closed
thomas-fossati opened this issue Mar 14, 2021 · 0 comments · Fixed by #153
Closed

more clarity around delegation revocation for non-STAR certs #144

thomas-fossati opened this issue Mar 14, 2021 · 0 comments · Fixed by #153
Assignees
Labels
ACME STAR Delegation secdir review Security Directorate last call review

Comments

@thomas-fossati
Copy link
Collaborator

https://mailarchive.ietf.org/arch/msg/acme/XF0qZ5Ba2ldx4Dxyuyo6vUV8-FA/

Section 2.4 is not sufficient to explain the revocation processing.
Only the NDC has the private key needed to make the ACME revocation
request, but this does not get stated in the text.  Also, it is not
clear to me how the NDC knows where to send the revocation request
since the IdO is the ACME account owner.  In addition, the phrase
"would create a self-inflicted DoS" needs more explanation.
@thomas-fossati thomas-fossati added ACME STAR Delegation secdir review Security Directorate last call review labels Mar 14, 2021
thomas-fossati added a commit that referenced this issue Mar 16, 2021
* State that NDC holds the private key which can revoke the associated
  cert;
* Explain how NDC could learn the revokeCert URL;
* Reword "self-inflicted DoS".

Fixes #144
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ACME STAR Delegation secdir review Security Directorate last call review
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant