Repository navigation
feat(go): key vendor backends through the encrypt guest (CIP-5311) - #1532
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,
|
f6e5996 to
dda3a35
Compare
59e08f7 to
d375388
Compare
dda3a35 to
fe5023c
Compare
c6c6614 to
d6e2eda
Compare
40e1527 to
cbe721d
Compare
d6e2eda to
9ca407d
Compare
9ca407d to
9d9c90e
Compare
cbe721d to
76ed2f2
Compare
9d9c90e to
780fdff
Compare
76ed2f2 to
6f35f29
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 guest drops the per-settle and v2 paths and the |
780fdff to
c905ced
Compare
6f35f29 to
747d42f
Compare
|
Replaced by #1630, in the new stack #1633. The code is the same, rebased onto the latest |
Layer 8 of the CIP-5203 stack. Implements CIP-5311 (ADR-0014).
stack-kms-vendorand the four vendor crates. A vendor request is a step of the step loop: the guest pauses with the signed request, and the host performs it, as it does for ZeroKMS. A credential is a step too. The host supplies short-lived credentials only: AWS temporary credentials, or an OAuth or Vault token. There is no RSA in the guest; the GCP service-account login is behind a default feature.WithKeyVendor,WithKeysetRecords,WithDefaultKeyset,WithRootKeyTTL,ErrNoZeroKMS. The vendor types areAWSKMS,GoogleCloudKMS,AzureKeyVault,VaultTransitandStaticKey. Credential seams are added; no vendor SDK is added togo.mod.Decisions are in
docs/plans/2026-11-05-key-vendor-backends-decisions.md(CIP-5311 section).