Repository navigation
security: persist one-time STEP_UP redemption across process restarts - #87
Merged
Merged
Conversation
… survives service restart
…edger commits redemption
… and invalid storage
…e-host limitations
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Nov 2, 2026
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.
Follow-on to #86. Post-approval authorization may be granted at most once per prior STEP_UP receipt, even after server restart: an operator-controlled absolute replay directory stores SHA-256-derived opaque marker names under an owner-private 0700 directory. Creation is atomic across local processes, uses exclusive creation and fsync before acknowledging permit, and fails closed on missing/insecure/unwritable storage. Synthetic CI tests rejection of duplicate redemption across separate Node processes. No customer data or signing keys in the ledger. Does not claim cluster-wide transactional guarantees: production multi-node storage and external reviewer evidence are still tracked in #80/#82.