I want a centralized way to manage keys and secrets. And some service users with little privileges over a subset of the secrets. Ideally, a service user only should be able to read its own subset of secrets. So, let’s say, if a container gets pwned it will only read its secrets and no more. It should be FOSS and self-hostable.
And a beautiful nice-to-have feature would be access log, to know who read what and when.
My only experience with something similar is Hashicorp Vault, but I don’t want to be near any Hashicorp stuff ever again.
Do you know a FOSS alternative to Vault?
OpenBao, fork from vault
Infisical?
Why didn’t you like Hashicorps Vault? I want to know for my own edification.
Recently they changed their license at a drop of the hat, then got purchased by IBM.
Can’t believe that’s gone through. They took JBoss when they bought RedHat so now it doesn’t have to compete with Websphere and when they bought HashiCorp Openshift doesn’t have to compete with Nomad. At this rate they’ll buy CyberArk and then that’s no more competition with Vault.
To make matters worse, Red Hat who own Ansible are also owned by IBM.
All hail International Business autoMation
There’s a little overlap with things like Terraform but it’s not as bad as if they bought the companies that owned Chef or Puppet.
Vault features are cool. I really like it. But with Hashicorp now there is this big risk of “rug pulling” regarding its license.
The wise thing, in my opinion, is to avoid this company as much as possible.
Can’t speak for OP, but the Vault software itself is fine. It’s their recent change in licensing that has a lot of people upset and looking for alternatives:
https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license
That is why today we are announcing that HashiCorp is changing its source code license from Mozilla Public License v2.0 (MPL 2.0) to the Business Source License (BSL, also known as BUSL) v1.1 on all future releases of HashiCorp products. HashiCorp APIs, SDKs, and almost all other libraries will remain MPL 2.0.
BSL 1.1 is a source-available license that allows copying, modification, redistribution, non-commercial use, and commercial use under specific conditions. With this change we are following a path similar to other companies in recent years.
Bitwarden now has their own secrets manager!
https://bitwarden.com/products/secrets-manager/
Ignore the enterpriseyness of that link. Once you log in normally just make an org and you should see the option to use secrets manager. It’s free for up to two orgs.
They just added a fee so that AWS can’t copy it without paying. What’s the big deal.
It’s no longer open source. Big Deal in my books.
Have you tried a key hook and a safe?
Sorry. Couldn’t help myself
