OpenBao Rust Crate 0.11.0 #13
Closed
eldryoth
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
openbao 0.11.0 Release Notes
Status: in development.
Readiness: implementation complete locally and local release gates pass; wait
for external pentest and CI validation before tagging.
Version
Summary
0.11.0is the Transit advanced key-management line. It focuses on BYOK/importendpoint wrappers, reversible Transit key soft deletion, global/cache
configuration, and certificate/CSR helpers while keeping raw private or
symmetric key material out of the default endpoint wrappers.
Remaining
0.11.0planned work: none. The local release-gate components andthe OpenBao
2.5.4integration smoke test pass locally; this candidate iswaiting for external pentest feedback and GitHub CI validation before the
v0.11.0tag.Added
ciphertext as
SecretString, reject empty ciphertext constructors, and redactciphertext/context fields from
Debug.verification/encryption keys that do not carry private key material.
transit-importsoftware wrapping helper that follows OpenBao'sdocumented AES-KWP/RSA-OAEP flow and returns the import ciphertext as
SecretString.as redacted
SecretStringvalues.Security Notes
path-validation, and secret-encoding behavior before tagging.
Client::request_json_with_retrynow acceptsRetryableMethodinstead ofarbitrary
reqwest::Method, preventing accidental retries of non-idempotentOpenBao write operations.
AdminBootstrapuses KV v2 CAS for secret-value convergence where OpenBaosupports it, and the security policy now states that all bootstrap plans
still require external serialization for ACL policies, AppRole settings, and
other read-compare-write operations.
visually ambiguous or percent-encoded path input.
0locally. BYOK exportnow takes
Option<u64>for version selection.Stringdatawhile keeping signatures secret-aware and redacted.
deprecated; use SHA-256 or SHA-512 for new deployments.
into
SecretString, avoiding an unnecessary duplicate plaintext copy whilerelying on
SecretStringzeroization on drop.unreachable!panic path.%{branch because policypath validation rejects percent characters before serialization.
wrappers. For private/symmetric imports, callers fetch the wrapping key, wrap
key material externally through an HSM, OpenSSL, or a reviewed crypto
library, and pass only the base64 BYOK ciphertext blob. Public-key-only import
constructors carry public material.
transit-importhelper is non-default and software-only. It is anergonomic helper for audited development and automation use; it depends on an
audited OpenSSL 1.1.1+ runtime baseline and is not an OpenBao, HSM, FIPS,
certification, or post-quantum security claim.
values because leakage may enable unintended import workflows.
private key material remains inside Transit.
Security And Stability Gate
OPENBAO_SKIP_INTEGRATION=1 scripts/release_0_11_gate.shscripts/openbao_integration.shmetadata, clippy default/all-features, tests default/all-features, doctests,
docs, package verification, dependency policy, RustSec audit, SBOM
generation, and the pinned OpenBao
2.5.4dev instance smoke test.green.
This discussion was created from the release OpenBao Rust Crate 0.11.0.
Beta Was this translation helpful? Give feedback.
All reactions