Repository navigation
feat(sending): expose retained key inventory for deployment guards - #1072
Merged
Merged
Conversation
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.
Adds a bounded operator inventory so deployment tooling can reject unsafe key retirement and reuse of retired operator-recipient versions.
-sending-protection-key-inventoryemits one schema-1 JSON snapshot of stored policy identity, retained key requirements, and permanent recipient commitments, with no account/message identifiers, addresses, secret bytes, or audit actors.Feedback and owner-notice HMAC references are separate from operator-recipient versions. Current authorized notice attempts keep their keys pinned beyond nominal expiry; superseded expired attempts do not. Corrupt policy, unresolved notice references, timeouts, and oversized inventories return a fixed error and no partial JSON. Normal startup migrations still precede the read-only command. Defaults, public HTTP/client APIs, and compiled sending contract level remain unchanged.
Validation:
Coordinated deployment integration: tokencanopy/e2a-ops#415. Inventory snapshots do not fence concurrent operator changes; deployments must serialize policy/secret administration. This PR does not activate policy or implement the subsequent compatibility-floor and billing recovery journal.