Repository navigation
docs(ocsp): say the node renews its OCSP responder after a CA re-key - #137
Merged
Merged
Conversation
Refs CryptOS-PKI/cryptos-node#383 Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Contributor
Author
|
Closing summary: the rotation docs now say the node renews its delegated OCSP responder after a CA re-key, matching cryptos-node#386. |
This file contains hidden or 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
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.
What and why
Companion to CryptOS-PKI/cryptos-node#386. After a CA key rotation the node now re-mints its delegated OCSP responder certificate under the new key, instead of keeping the one the discarded key signed. I added that to the "Other keys are software keys by design" callout in the TPM deep dive (with the existing halfway-point renewal it describes) and to the
ca submit-rotationrow in the cryptosctl reference.Refs CryptOS-PKI/cryptos-node#383
Merge order: together with CryptOS-PKI/cryptos-node#386, after it.
Verification
How this was verified
npm ci --ignore-scriptsandnpm run buildin a fresh worktree: static files generated, no broken links reported.internal/init/run.go, which calls the responder'sensure; the re-mint condition is the new signature check ininternal/init/ocsp_responder.go.