Pass uses gpg along with the filesystem and git, so it is lightweight, and super-easy to backup offsite, as long as you guard your gpg keys separately. For those who want a GUI, QtPass[2] provides a simple GUI while using pass in the background.
Pass uses gpg along with the filesystem and git, so it is lightweight, and super-easy to backup offsite, as long as you guard your gpg keys separately. For those who want a GUI, QtPass[2] provides a simple GUI while using pass in the background.
The whole source code of bash pass [1] is almost as long as a single header file [2] from this C++ software. Plus pass already handles backup... Minimalist heh.
[1] https://git.zx2c4.com/password-store/tree/src/password-store...
[2] https://github.com/JFreegman/SpicyPass/blob/master/src/spicy...
tl;dr different strokes for different folks. I didn't write spicypass with the intent of replacing pass.
Yeah, that's the point of using Unix, and why pass is great for that.
One difference I see between this and pass is that spicypass is storing all the credentials in a single file. If you don't want to leak metadata with pass you have to add pass-tomb[1].
Anyway I just use pass (gopass actually) and I have no problems, it's a great improvement over a text editor.
[0]: https://github.com/dylanaraps/pash
[1]: https://git.sr.ht/~seirdy/dotfiles/tree/master/.config/shell...
And for the life of me I can not get it to prompt for the password in the terminal, which is infuriating.
First glance of SpicyPass looks promising in my eyes.
[0] https://play.google.com/store/apps/details?id=com.zeapo.pwds...
Do you know why the Play Store description says that it is no longer maintained? Is the app being published somewhere else?
Thanks for the info