$ tree .password-store
irc
├── efnet
└── freenodeHas anyone else here had the same thought? This guy seems to at least;
https://github.com/equivrel/password-store-encfs/blob/master...
Edit: spelling
Could use autofs to make it auto mount when pass accesses the mount point.
Thanks for the autofs hint, will try it and see how that works out re unlocking.
Frankly, just encrypt the entire drive. Otherwise, there will always be a leak somewhere. If not in the file structure, then in the swap.
The downside is a lack of control over complexity and the issue of passwords being strictly dependent on the salt. So, if one set of credentials is compromised, you would need update them all.
I've seen software that does this, but there are subtle details to consider to actually get it correct.
[edit] deleted paragraph that was supposed to be added to a different comment.
1. ./blah.sh | grep LookupKey exposes just as much information as pass -c LookupKey. If someone has access to your machine and you don't carefully prune your bash history file, then you're screwed. However, in the latter case, at least you get something at the cost of giving up security -- namely, the convenience of tab completion.
2. The only way to solve problem #1 in general is to have multi-stage authentication, where you authenticate to access to lookup keys and then authenticate again to access the passwords. That's achievable using pass and some Bash -- obfuscate file names and store a obfuscated -> actual mapping in a gpg-encrypted file, and write a bash script that does the ln -s'ing. And then the command that does that dumps you into a shell that doesn't record history.
I did this for a while but found it's a bit of PITA. Also, I can almost always come up with names that would be difficult to exploit without a lot of information about my life (bank_primary, bank_secondary; email/personal, email/business, email/spammy; server/personal, server/2011; and so on. I won't remember these verbatim, but once tab-completion reminds me of my options I typically recall which is which. And in case you're afraid in several years you'll forget which server you first purchased in 2011, you can always just pass -e server/2011 and explain which one you meant in subsequent lines.
- https://github.com/gustaebel/passext (Chrome)
or
- https://github.com/jvenant/passff (firefox)
"This is pre-alpha quality software, the result of a three
day project. It will crash your browser, leak your
passwords and destroy your home. This is actually my first
Chrome extension and I am no expert javascript programmer."
YMMVIt actually works better (for me) than 1password which was always a little flaky at recognizing a website after any kind of site update.
https://play.google.com/store/apps/details?id=com.zeapo.pwds...
There's a iPhone one I cannot comment on.
Some examples of using it: http://joshtronic.com/2014/02/17/using-keyring-access-on-the...
I've given up on it, but I'd like to know if anyone might have found something that I overlooked.
There's also the issue that if it does export something, you have to accept every exported item individually. If you search the internet, you'll find people who wrote scripts for "automatic accept-clicking."
But as I said, once I looked up what it exported, I noticed that it was far from complete.But maybe there's some command line option buried somewhere that will accomplish what I wanted to do...
The whole export thing is just terribly broken.
edit: looks like there's an iPhone app as well. See http://www.passwordstore.org/
* git integration.
* Separate file for each secret, so that I can store the password on the first line and then other sensitive account details on subsequent lines.
* -c flag for copying passwords to clipboard (but only copies the first line of the file, so it doesn't interfere with the usecase above)
* tab completion for user account names. However, this comes at a slight cost to security -- anyone with access to your machine (or git repo) can see all of the websites / accounts for which you have a password.
* Everything happens via the file system and secrets are just gpg encrypted text files. So it's really easy to implement new utilities on top of your password store. This is true for this solution as well, but somehow having separate files for each account makes it safer to implement utilities that do account management.