Oh, yes, that's for sure. You need to change everything, every password. I was
just answering the question of how to remove a key id.
Also, if using a shared remote repo, the write access must be revoked from
beforehand, else the leaving user can re issue pass init... and add their key.
Cheers
On 11/8/18 4:28 PM, HacKan wrote:> Simply issue pass init again with the
new keylist, that's it :)
not really, since the person who left the team can check out an old copy
of the repository and use the key which was valid at that time to
decrypt all passwords.
I am afraid all passwords must be
Hi Gaspar!
Simply issue pass init again with the new keylist, that's it :)
Cheers!
On November 8, 2018 9:28:20 AM GMT-03:00, "José Gaspar"
wrote:
>Hi,
>
>I have a quick question when using pass with multiple GPG keys.
>
>I like the idea using pass in my team and I wonder how pass deals when
On 18-11-08 12:41:36, Kevin Lyda wrote:
You should assume they have all the passwords in pass. So you'd want to
remove their gpg key - I think you just do that with git init and then a
list of the gpg id's you want to keep. Then you need to change all your
passwords.
Kevin
Agreed, it's the
You should assume they have all the passwords in pass. So you'd want to
remove their gpg key - I think you just do that with git init and then a
list of the gpg id's you want to keep. Then you need to change all your
passwords.
Kevin
On Thu, Nov 8, 2018 at 12:29 PM José Gaspar wrote:
> Hi,
>
>
