[asimilator]

Seems similar to 'pass' (http://www.passwordstore.org) but IMO without pass' killer feature: git integration. pass manages passwords as a directory tree of gpg encrypted files which can be easily synchronized with multiple machines using built-in git integration (not to mention all the other benefits of version control, like undo/redo, history, etc).

[troyjfarrell]

Version control is really cool for this sort of information. Unfortunately, pass leaks information in filenames, which is a pretty big problem for some uses. In my opinion, the version control needs to be built into the application to avoid all the potential side channel information leaks.

[dkbrk]

I think it's important to point out that whether something like this matters depends entirely on your security model. For example, an attacker learning that I have a gmail account isn't very useful information, so I don't consider it confidential. This is a property of most of my credentials.

The way pass is built on top of gpg encrypted files in git is at the core of its robustness and simplicity. Creating an encrypted, version controlled store from scratch would be a not insignificant engineering effort, though something similar could be accomplished, for example, by putting the password store inside encfs.

If the mere existence of a credential is considered confidential information, a simple measure to bypass this flaw is to give it a meaningless randomly generated name such as "faithful_iceberg".

[mataug]

I've been using pass for a while now. It's quite mature and stable. I use it with git and put it through encfs and sync it with dropbox. Works quite well.

I hope this matures enough to compete with `pass`

[pcpolice]

Hm, that's what put me off pass. I want to manage my own dotfiles git repository.

[asimilator]

The git integration is optional. If you don't turn it on you just have a .password-store directory of gpg encrypted files. I don't see why you couldn't add that to your dot files git repo.