pw

Check out pw, my alternative to pass, designed because of the reason you mentioned: I don't want my password manager to leak the list of services I use. https://github.com/gioele/pw In pw each password database is a single file, the internal indexes are random IDs. Each line in a database is a serialized GPG file with a password and associated metadata. The file format is git-compatible and everything can be managed with standard command line tools.

You dont necessarily need "integration" to achieve this. You can always put a file under version control. I've stole some links from https://github.com/gioele/pw to show that there are downsides to the separate files approach: http://nms.csail.mit.edu/projects/ssh/ http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-2666

> It sounds like a lot of us have been making password managers recently. Here's one I made a few days ago: > https://github.com/ojensen5115/pw/ I made one as well. Same name, totally different philosophy. ;) https://github.com/gioele/pw

I'll use this as an opportunity to give a shout out for my own unix password manager that I started writing because I did not like some design choices of pass: pw [1]. From the homepage: > pw is an alternative to pass, keepassx and other similar programs. > The main points of pw are: > * The passwords are stored using a simple line-based text format. > * Passwords can be protected using public-key encryption or symmetric encryption. Or both. > * No information about the accounts is stored in clear-text. > * All the work is done using only GPG and Unix tools. > * The output is easy to use in pipeline with other tools. > * Follows the XDG Base Directory specification: no clutter in your home directory. [1] https://github.com/gioele/pw