Certificate lifecycle: ACME revocation #42
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deferred from the per-name ACME work (spec:
obsidian/Personal/Projects/edge-router/specs/2026-10-22-remove-tpm-openbao-encryption-design.md).Revoke a certificate with the CA, as distinct from deleting it locally.
Why it waits: the spec deliberately separates the two. A name leaving the route table drops its row and resolver entry via reconciliation and does not revoke — revocation is for key compromise, and a decommissioned route may legitimately return. So revocation is an explicit operator action for a different situation, not part of the cleanup path, and nothing in the removal work needs it.
Note for whoever picks this up: revocation needs the account key that issued the certificate, so it must work after the key has been re-issued or the account rotated, or it will silently fail on exactly the certificates most likely to need revoking.