When combined with a yubikey set to decrypt only on touch this setup has a very low attack surface compared to other browser password managers.
I since switched to a separate on-device key for "low value" passwords and keep the interesting stuff (e-mail pwds) under the yubikey protected key (which does requires touch).
Did you find a better solution?
Apparently there is a new "cached" option for the touch settings "Touch is cached for 15s after use (valid from 4.3)." Which would work for your use case but also neglect some/most? of the security advantages.
any recommendations for OS X? is it worth building from source and/or getting it working outside of brew?
From memory I think autocomplete worked for pass once I started using antigen.
I have the following plugins in my .zshrc plugins=( zsh-syntax-highlighting git iterm2 dotenv osx zsh-autosuggestions )
and also run antigen with user bundles for zsh-autosuggestions zsh-syntax-highlighting zsh-completions
Some magic somewhere in the above provided autocomplete for me with pass.
I hope it helps.
Then whenever you insert something into the `pass` database (which is just a directory tree full of encrypted plaintext files) the tool uses the public key to encrypt the password (or anything else):
pass generate --no-symbols shopping/ebay 16
Later, when you want to read a password, you ask pass to decrypt the file using the private key from your keypair: pass shopping/ebay 16
The difficulty is really all in managing the keys, which can be quite a faff to set up and then manage.
If you're only using gpg for `pass`, IMO it's easiest to copy the keypair (which gpg generated) to all your other machines.A quick web search brought up a gist [0] which shows how to quickly get up and running on a single machine.
If you want to use it on another laptop/desktop/*nix-like machine you'll need to export both your public and private gpg keys and then import them on the other machine. When using a phone you have to do something similar. The Android clients were fairly straightforward, but Pass for iOS had a very, very clunky way of getting the keys across. Regardless, it boils down to this: get the gpg keypair on all of the devices and then get them all using the same git repo for pass.
[0]: https://gist.github.com/flbuddymooreiv/a4f24da7e0c3552942ff
Luckily I'm technically minded, so it's not too hard to manage my GPG keys or manage syncing the git repo every now and then.
What it lacks in swish UI and automagically-configured browser extensions it gives in configurability, privacy, control over data, and freedom.
[0]: https://www.passwordstore.org/