Heya,
We use this in our company, we have a repository of pub-keys of all the team
members.
They have to be signed by all the members that need to encrypt for them.
Inside the password-store you can per-folder set a .gpg-id file that lists the
key-ids of all involved.
You can then do a pass init on the folder to re-encrypt using everyones gig
pub-key.
Hope that is at-least a clear explanation of the basic way to do what I think
you want to do ;-)
Greets,
Anne Jan Brouwer
> On 5 nov. 2014, at 12:44, Alfredo Palhares <[email protected]> wrote:
>
> I've been using pass personally and love the simplicity. I don't even
> depend on it to decrypt a password which makes it pretty much failsafe.
>
> Now I am looking on creating a passwords repository to share across a
> whole team. So the same file would be able to be decrypted by multiple
> people.
>
> Lets says we have the following tree:
>
> ├── README.md
> ├── Finance
> │ ├── Banking
> │ │ └── A_bank
> │ └── Someservice
> └── Operations
> ├── Cloud
> │ └── NewFancyService
> └── RootPasswordOnXServer
>
> I would like to set some rules to set who can can encrypt and decrypt
> the credentials. So only the finance team would be able to see financial
> services and the operations team would only have access to the
> operations related credentials.
>
> Setting teams or groups of people would be great too.
>
> Finally push and pulling the changes from upstream would be awesome to
> keep the repositories in sync.
>
> Is this something password-store was meant to do ?
>
> --
> Regards,
> Alfredo Palhares
> _______________________________________________
> Password-Store mailing list
> [email protected]
> http://lists.zx2c4.com/mailman/listinfo/password-store
_______________________________________________
Password-Store mailing list
[email protected]
http://lists.zx2c4.com/mailman/listinfo/password-store
