You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(go): key vendor backends through the encrypt guest (CIP-5311) - #1630
Layer 8 of the CIP-5203 stack. Implements CIP-5311 (ADR-0014).
The encrypt guest links stack-kms-vendor and 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.
Go API: WithKeyVendor, WithKeysetRecords, WithDefaultKeyset, WithRootKeyTTL, ErrNoZeroKMS. The vendor types are AWSKMS, GoogleCloudKMS, AzureKeyVault, VaultTransit and StaticKey. Credential seams are added; no vendor SDK is added to go.mod.
A vendor-only client needs no CipherStash credentials.
One guest with all backends.
Tests: hermetic Go tests with the static key, and with AWS through a fake RoundTripper that checks SigV4 and call counts.
Decisions are in docs/plans/2026-11-05-key-vendor-backends-decisions.md (CIP-5311 section).
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
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.
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).