Pass: Difference between revisions
From DWIKI
m (→Links) |
|||
Line 4: | Line 4: | ||
*[http://www.passwordstore.org/ Homepage] | *[http://www.passwordstore.org/ Homepage] | ||
*[https://sig-io.nl/?p=399 Read passwords from the 'pass' passwordstore into ansible] | *[https://sig-io.nl/?p=399 Read passwords from the 'pass' passwordstore into ansible] | ||
*http://superuser.com/questions/520980/how-to-force-gpg-to-use-console-mode-pinentry-to-prompt-for-passwords | |||
=Setting up a shared pass git repository= | =Setting up a shared pass git repository= |
Revision as of 13:40, 1 February 2016
Simple password manager using gpg
Links
- Homepage
- Read passwords from the 'pass' passwordstore into ansible
- http://superuser.com/questions/520980/how-to-force-gpg-to-use-console-mode-pinentry-to-prompt-for-passwords
On server pass.example.com create user passuser Then as this user:
mkdir pass.git git init --bare pass.git
On your workstation:
If you don't already have gpg key:
gpg --gen-key
and import pubkey(s) of other user(s):
gpg --import hisid
To make gpg use group, add to .gnupg/gpg.conf:
group ourgroup yourid hisid default-key <your key id> ?
Slightly less secure but very convenient:
ssh-keygen
and then add .ssh/id_rsa.pub to .ssh/authorized_keys on server
Then init pass:
pass init ourgroup pass git init pass git add remote origin passuser@pass.example.com pass git push
Now all it takes to add keys is:
pass add someserver/someaccount pass git push
On system of hisid you run the same pass init/git instructions, and then
pass git pull
ACHTUNG any user who edits or adds keys needs the public keys of all group members!