Expand description
Pluggable signing / key-store backends.
The agent is a proxy: incoming NEW_KEY / SIGN / VERIFY messages are
dispatched to a Backend trait object. v1 ships a single implementation,
vault::VaultBackend (a Vault-compatible transit engine: HashiCorp Vault or OpenBao),
but the trait is deliberately backend-agnostic so additional stores
(db-keystore, 1Password, cloud KMS, an internal TPM-backed signer, …) can be
added later without touching the protocol or the connection handler.
Modules§
- spiffe
- Vault-compatible (Vault or
OpenBao)transitbackend authenticated with a self-minted JWT-SVID instead of a static token. - vault
- Vault-compatible (
HashiCorpVault orOpenBao)transitbackend, authenticated with a static token (X-Vault-Token).
Structs§
- KeyMetadata
- Value-free metadata for one key, returned by
list. - KvSecret
- A KV-v2 SECRET read: the stored bytes wrapped in
Zeroizingplus the version they came from. - KvValue
- A KV-v2 value read: the stored bytes plus the version they came from.
- NewKey
- A newly created (or imported) key.
- Public
Key - A key’s public material plus the metadata
get_public_keyechoes back. - X509
Bundle - Trust-domain X.509 bundle material, ready for Workload API response assembly.
- X509
Cert Request - Parameters for a DNS/IP-SAN X.509 leaf issuance (a TLS cert, not a SPIFFE
SVID). Mirrors
Backend::issue_x509_svidbut binds DNS/IP SANs and a common name instead of a SPIFFE URI SAN. - X509
Svid - An issued X.509-SVID leaf set from a PKI backend.
Enums§
- Backend
Error - Errors a backend may return. Service adapters map these to canonical gRPC statuses.
- Native
Algorithm - A post-quantum algorithm a
Backendmay natively custody and operate on in place: the private seed never leaves the backend. - Sign
Options - Backend signing mode for operations whose wire format fixes an algorithm.
Traits§
- Backend
- A pluggable key-store + signing backend.