Repository navigation
feat(stack-kms-vault): HashiCorp Vault Transit key vendor backend (CIP-5310) - #1529
Conversation
|
|
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,
|
37aebb1 to
bfdd74a
Compare
3721ee0 to
8d2579a
Compare
bfdd74a to
95da1a1
Compare
8d2579a to
14f5bdd
Compare
95da1a1 to
0642192
Compare
089a740 to
ee3980e
Compare
0642192 to
3dd5da9
Compare
ee3980e to
f9afbdf
Compare
447acd9 to
f9b71cc
Compare
|
Scope reduced (2026-11-12). This branch was rebuilt from one final tree by path, and the follow-up PRs #1555 to #1563 were folded in. The plan is In this PR: the one-item |
677cc5a to
f07f74a
Compare
f9b71cc to
aeb384d
Compare
|
Replaced by #1627, in the new stack #1633. The code is the same, rebased onto the latest |
Layer 5 of the CIP-5203 stack. Implements CIP-5310.
stack-kms-vault: a hand-written Transit client (encrypt,decrypt,rewrap).stack_kms_vendor::boundbinds the AAD into the wrapped key itself. Vault ignorescontexton a key that is not derived, and Azure (CIP-5309) needs the same mechanism.vault server -devCI job.stack-kms-vendorrelease group.Decisions are in
docs/plans/2026-11-05-key-vendor-backends-decisions.md(CIP-5310 sections).