What do you use for managing secrets in your environment?
I am looking for a centralized way to distribute db connection strings and credentials, public keys, API keys and such in a small'ish environment.
The goal is to have as few secrets on the client machines as possible, and have easy rotation of certain share passwords.
#Hashicorp #vault, #bitwarden secrets manager seem to fit. I would like to hear of your experiences.
Goddammit, #Hashicorp: why you telling me I need to install #Docker on my EL10 VM rather than letting me use #PodMan???
#BSI WID-SEC-2025-0933: [NEU] [mittel] #Hashicorp #Vault: Mehrere Schwachstellen
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Hashicorp Vault ausnutzen, um Sicherheitsvorkehrungen zu umgehen und um Informationen offenzulegen.
https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0933
And if you were hoping that the #copyleft from #AGPL would somehow prevent #Redis from relicensing back to SSPL or worse, you might want to read their #CLA, while remembering what #Hashicorp did:
https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md
I put together a quick blog post on how to get up and running with Consul and Docker using DockerConsulAgent.
https://open.substack.com/pub/zentourist/p/bridging-docker-and-consul-with-elixir?r=1niag&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false
💼 TECH | 🇺🇸 US
🔴 IBM Beats Q1 Forecasts, Holds 2025 Outlook
🔸 Q1 EPS $1.60 vs. $1.40 expected; revenue $14.54B.
🔸 Software +7%, hybrid cloud (Red Hat) +12%; consulting -2%.
🔸 Expects $13.5B free cash flow & ≥5% revenue growth in 2025.
....aaaaaand #OpenBao (the fork of #Hashicorp #Vault) is on its way to @opensuse #Tumbleweed in the latest version 2.2.1. Since 2.2.0 the webui is included in OpenBao, so this can be a full replacement for Vault!
Looking forward to doing more testing with it!
In case you want to try it out, here is a #vagrant #libvirt setup using #Ansible to prepare an OpenBao server VM and a client using a secret.
https://codeberg.org/johanneskastl/openbao_vagrant_libvirt_ansible
Want your Docker containers to register automatically in your dev Consul environment? I wrote a lightweight container to do that for you. Check it out: https://github.com/zenchild/docker-consul-agent
#HashiCorp #consul #ConsulProject
#bitBlog Managing dynamic secrets with #Hashicorp Vault & Boundary
https://blog.bitexpert.de/blog/dynamic_secrets_with_vault_boundary
HashiCorp Certified: Terraform Associate (003) http://leanpub.com/courses/leanpub/terraform-associate by Mattias Fjellström is the featured online course on the Leanpub homepage! https://leanpub.com #CloudComputing #InfrastructureAsCode #hashicorp #courses #terraform
Just wrapped up our live session where we dove into setting up HashiCorp Consul policies!Missed it? Catch the VOD on our channel and stay tuned for more DevOps deep dives.
Follow @theDevCastOps for more live infra and cloud-native content!
Dear #AWX users out there (AWX as in Ansible, not AWS as in Amazon...),
does anyone have good pointers on connecting AWX and #Hashicorp #Vault / #OpenBoa **without** having to define each secret/credential again in AWX?
I have set up a basic connection according to the documentation: https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault
And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.
But having to define a AWX credential for each secret that I need to pull from Vault/OpenBoa sounds like a lot of unnecessary duplication.
(Yes, I know you can manage AWX via Ansible. We do that already. But still, you need to define the credentials in your code somewhere for the automation to create it in AWX)
🚀 Excited to share that I’ve been selected as a HashiCorp Ambassador! 🏅
Honored to join a global community of cloud innovators & contribute through content, mentoring, & collaboration.
Let’s build scalable, secure systems! 🌍🔧
I'm excited to announce that I've been selected as a HashiCorp Ambassador for 2025.
Our journey with HashiCorp started early on with Vagrant to simplify project virtualization. In 2019, we chose Nomad over Kubernetes for its simplicity and scalability. Last year, we implemented Boundary & Vault for simple and secure remote access based on user identity.
If you want to know more about Nomad or Boundary, let me know.
Uuuuuuuh, #OpenBao (the open source fork of #Hashicorp #Vault) just released version 2.2.0 and now includes the UI, that was missing so far.
The package for @opensuse was adapted, tested and worked out fine. Will soon be available in #Tumbleweed!
If you want to test this out, feel free to use this vagrant-libvirt setup of mine:
https://codeberg.org/johanneskastl/openbao_vagrant_libvirt_ansible
#openSUSE #secretsmanagement #opensource #hellyeah #vagrant #libvirt
"#IBM Completes #Acquisition of #Hashicorp, Creates Comprehensive, End-to-End Hybrid #Cloud Platform"
End of an era - but start of a new one! Watch to see how this pans out. $IBM will 'blue-wash' $HCP, but hope for a soft touch like with #RedHat. #Culture will be key!
"#IBM Completes #Acquisition of #Hashicorp, Creates Comprehensive, End-to-End Hybrid #Cloud Platform"
End of an era - but start of a new one! Watch to see how this pans out. $IBM will 'blue-wash' $HCP, but hope for a soft touch like with #RedHat. #Culture will be key!
