5 ms·
I thought SOPS with age is what we were doing now. Do we need yet another tooling? https://github.com/getsops/sops https://github.com/getsops/sops
by moontear 7mo ago
I thought SOPS with age is what we were doing now. Do we need yet another tooling?
https://github.com/getsops/sops https://github.com/getsops/sops
- patabyte 7mo agoSOPS with Age is simple, and simple is good. I strongly recommend this approach.
- sam_lowry_ 7mo agoSOPS is simple? You are kidding me. Pass from https://www.passwordstore.org/ https://www.passwordstore.org/ fame is simple. SOPS is ultra-complicated for a security tool.
- sevg 7mo agoI dunno, it seems mostly simple to me. You have a .sops.yaml with some Age public keys, and then you run “sops secrets.yml” to create an encrypted file.
- jmholla 7mo agoCan you explain what you find complicated about sops? I've used it with ease for the last two years, both personally and professionally.
- oulipo2 7mo agoThere's also https://github.com/jdx/fnox https://github.com/jdx/fnox
- moontear 7mo ago"also" is a strong word for a project this young. It was started in October 2025, does not have any issues (at all) and is completely vibe coded. Not starting a discussion about security & vibe coding now, but I wouldn't blindly recommend such a nascent project if compared to something mature like SOPS.
- elevation 7mo agoOne of the first tasks I had for Claude was to build a protected KV store out of keepassx.cli. Out of the box I got a beautiful gui for seeding initial secrets while giving me a nice scriptable, non-interactive tool for injecting secrets into infrastructure bootstrapping.