Repository navigation
feat(stack-kms-vendor): keyset records, derived data keys and the static key backend (CIP-5306) - #1625
Conversation
…tic key backend (CIP-5306) The vendor seam (wrap, unwrap), keyset records, the derived data key mode with the root key TTL in the key source, the key router (ZeroKMS and at most one vendor, by keyset id), the static key backend, the transport seam, the shared credential cache, the contract suite and the fixture harness. The vendor and mode bytes are bound into every derived key.
|
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true |
Mutation testing (cargo-mutants,
|
Layer 3 of the CIP-5203 stack. Implements CIP-5306 (ADR-0013).
stack-kms-vendor, with theKeyVendorBackendtrait (wrap,unwrap,sleep). Each vendor crate implements only this trait.KeysetRecordis a versioned record, written asstack-keyset:+ base64url, withcreateandrewrap.KeyRouterholds ZeroKMS and at most one vendor, and routes by keyset.retry(backoff on throttling), theVendorTransporttrait, and a shared contract suite.stack-encryptdoes not change. Decisions are indocs/plans/2026-11-05-key-vendor-backends-decisions.md(CIP-5306 section).