4 ms·
You may want to look at pass, which is pretty lightweight scripting around gpg to store passwords in multiple files. Some tradeoffs required, but works well and
by Xylakant 10y ago
You may want to look at pass, which is pretty lightweight scripting around gpg to store passwords in multiple files. Some tradeoffs required, but works well and fully auditable
- Freak_NL 10y agoPass¹ is very nice, and you can even share a part of your password library with someone else by using their GPG public key (encrypting just those files with both your keys) and sharing the shared directory via some sharing utility such as SyncThing². Pass also supports using git for change management. 1: https://www.passwordstore.org/ https://www.passwordstore.org/ 2: https://syncthing.net/ https://syncthing.net/
- storrgie 10y agowhy use syncthing when pass supports git?
- Freak_NL 10y agoBecause with git you have to explicitly push. Both have their valid uses; I use the git solution for a devops password database shared with a small number of colleagues. I use SyncThing to share a common subdirectory of a private password database with my partner. SyncThing has the benefit of transparently handling the synchronisation behind the scenes for me. Whenever I place something in pass in the 'shared' subdirectory, it will end up in her database as well as soon as both our devices are online.
- deleted 10y ago[deleted]
- zeveb 10y agoIf pass would encrypt file names I'd switch to it immediately. But unenecrypted filenames are a non-starter for me. Right now I'm ginning something up based on the PasswordSafe format and the pass interface, but it'd be great not to have to reimplement the wheel.