←back to thread

Show HN: A local secrets manager with easy backup

(github.com)
16 points RaiyanYahya | 1 comments | 29 Jun 25 09:30 UTC | HN request time: 0.222s | source
Show context
CBLT ◴[02 Jul 25 03:34 UTC] No.44440041[source]▶
Skimmed the readme, seems like it's not AEAD? I don't see any reason to use a tool that's not AEAD.

Also, while I get the appeal of just storing it all in a giant JSON, I don't really feel that's the final word in simple storage formats. I'd personally just use SQLite, or some other format I could rsync.

replies(3): >>44440127 #>>44440230 #>>44440720 #
renerick ◴[02 Jul 25 03:56 UTC] No.44440127[source]▶
Text formats have the advantage of better support in version control systems. SOPS does similar thing, it stores encrypted values in yaml/json, and from my experience using this approach with git it is indeed an improvement over, say, Ansible vault, which essentially turns text files into blobs
replies(1): >>44440233 #
1. CBLT ◴[02 Jul 25 04:21 UTC] No.44440233[source]▶
I use pass[0] which uses a flat directory structure and git. It works great! At $dayjob we have json lockfiles committed to git and merges get pretty gnarly. Not as big of a fan of just dropping it all in json. The toml lockfiles are a bit better in git.

[0] https://www.passwordstore.org/