passhole VS encpass.sh

What about something like passhole? Use your existing keepassxc database from the command line.

The KeePass format has been around for years. I don't really understand why people keep using pass, or why it bills itself as the "standard" Unix password manager.

There are also already command line KeePass utilities, like passhole [0] (mine) and keepassxc-cli.

[0]: https://github.com/evidlo/passhole

I wrote a pass equivalent for KeePass for this very reason [0]. KeePass doesn't leak any metadata because everything is contained in a single file.

[0]: https://github.com/Evidlo/passhole/

There is passhole for cli https://github.com/Evidlo/passhole

https://github.com/plyint/encpass.sh/archive/v${pkgver}/${pkgname}-${pkgver}.tar.gz

The difficulties mentioned in the article with passing secrets on the command line is one of the reasons why we wrote encpass.sh (https://github.com/plyint/encpass.sh). We had a similar need for a lightweight solution for managing secrets for simple shell scripts on our local workstations and in restricted environments. Bonus, it can be easily customized with extension scripts to adapt functions for your own specific needs. See our keybase extension for an example -> https://github.com/plyint/encpass.sh/blob/master/extensions/...

We made an extension for encpass.sh that stores secrets in Keybase (https://github.com/plyint/encpass.sh/blob/master/extensions/...) if that sort of thing is of interest to you. Outside of personal secrets, it can be used as a sort of low cost stand in for shared secrets that you might use something like Vault for in a team environment.