3 ms·
My main reason to not use pass is that I can't allow multiple private keys to unlock the password store. I don't want to transfer my private key between all my
by raziel2p 9y ago
My main reason to not use pass is that I can't allow multiple private keys to unlock the password store. I don't want to transfer my private key between all my machines.
- corey_moncure 9y agoYou absolutely can do this. In your .gpg-id file, simply list the keys you want to encrypt for on separate lines. Every file below that .gpg-id file in the directory hierarchy will be encrypted for any of those keys to unlock.
- andrewstuart2 9y agoAlso you can re-init any time you want, listing multiple keys. This will go through all your passwords and re-encrypt them for each of the keys listed. That's how I got my phone set up with access (with its own locally-generated private key). If you want more granular key strategy, look at gopass [1], which is a pass-compatible binary that gives a little more granular control over key usage (IIRC), and is written in Go. [1] https://github.com/justwatchcom/gopass https://github.com/justwatchcom/gopass
- spapas82 9y agoWhy not transfer the private key? I encrypted it using a one-time pass and send it using email. I then decryped and installed to the other machine. Since I don't have the one time pass anymore the encrypted file is not usable anymore and I have the same key to both machines. Please explain any holes with that flow.