Security
OpenBao 2.7 Introduces External Key Management and Quantum-Safe TLS Support
The HashiCorp Vault fork adds hardware-backed keys, post-quantum cryptography, and PostgreSQL scaling—solidifying its position as a production-ready open-source secrets manager.
InfoQ
OpenBao, the open-source community fork of HashiCorp Vault, has reached version 2.7 with significant additions to its cryptography and storage capabilities. The release delivers external hardware security module (HSM) and key management service (KMS) integration, support for quantum-resistant algorithms in TLS connections, and expanded read scaling for PostgreSQL-backed deployments.
Why OpenBao Matters#
OpenBao emerged from frustration with HashiCorp's 2023 decision to relicense Vault under the Business Source License, replacing its open Mozilla Public License. The fork reflects both ideological and practical concerns: vendors had placed enterprise capabilities—namespaces, HSM support, and scalability features—behind proprietary licensing walls. As part of a broader industry pattern that also birthed OpenTofu from Terraform and Valkey from Redis, OpenBao aims to deliver equivalent functionality under genuine open governance within the Linux Foundation's Open Source Security Foundation.
New Capabilities in Version 2.7#
External Key Support: The PKI and Transit secrets engines can now use cryptographic material stored in external HSMs or KMS systems rather than storing keys inside OpenBao itself. This appeals to organisations managing sensitive root certification authority keys or other high-value material that must remain under hardware control.
Post-Quantum Cryptography: The release incorporates ML-DSA and ML-KEM algorithms into TLS listeners, certificate authentication, and the PKI and Transit engines. While this alone doesn't guarantee quantum safety—clients and surrounding systems must also adopt these standards—it enables operators to begin testing hybrid and post-quantum configurations ahead of anticipated government transitions around 2030.
PostgreSQL Horizontal Scaling: Following previous work on Raft-based read scaling, OpenBao 2.7 extends that capability to PostgreSQL deployments, allowing standby instances to handle read operations without burdening the primary.
Control Groups for Approval Workflows: A new ACL policy construct enables two-party review of sensitive operations, preventing any single authenticated user from acting unilaterally on high-risk paths.
Structural Changes and Trade-offs#
The release includes breaking changes reflecting the project's architectural evolution. The separate HSM distribution has been discontinued as the PKCS#11 plugin shifts to an external model. Vendor-specific auto-unseal mechanisms for major cloud providers (AWS, Azure, Google Cloud, Alibaba, Oracle) now live as plugins rather than built-in features. Authentication methods including Kerberos, LDAP, and RADIUS have also moved to the external plugin repository. The file storage backend has been removed entirely, reflecting its acknowledged unsuitability for production deployments lacking high availability and transaction support.

