diff options
author | Silvio Rhatto <rhatto@riseup.net> | 2013-09-10 14:00:42 -0300 |
---|---|---|
committer | Silvio Rhatto <rhatto@riseup.net> | 2013-09-10 14:00:42 -0300 |
commit | fa8858356ec9521795b86e677fd768f51789abbf (patch) | |
tree | 648c57720aec736d872c0fc3b05c315d7eee351d /index.mdwn | |
parent | 5c0574c296ba0a1f0951f5d217f05fad0f1fcb00 (diff) | |
download | keyringer-fa8858356ec9521795b86e677fd768f51789abbf.tar.gz keyringer-fa8858356ec9521795b86e677fd768f51789abbf.tar.bz2 |
Manpage: add init action and other changes
Diffstat (limited to 'index.mdwn')
-rw-r--r-- | index.mdwn | 13 |
1 files changed, 5 insertions, 8 deletions
@@ -164,15 +164,12 @@ Concepts Basic idea is: - - Encrypt stuff with ppl's gpg pubkeys and push the output in a git repo. + - Encrypt stuff with multiple users's gpg pubkeys and push the output in a git repo. - - Let ppl keep it in sync with the repo and the keys are shared :) + - Let users keep it in sync with the repo and the secrets are shared :) -For "key" it's meant anything as the script work with stdin and output things to -files, so it can be passphrases, private keys or other kind of info. - -It's possible to share keys using an encrypted mailing list, but the main -difficulty is to track the message where the keys are. +For "secrets" it's meant anything as the script work with stdin and output things to +files, so it can be passphrases, private keys or other kind of information. With theses scripts, the workflow is more or less like this: @@ -185,7 +182,7 @@ With theses scripts, the workflow is more or less like this: - You manually add it to git and push it to remote repositories. - - Optionally, other ppl pulls the changes but they dont need to + - Optionally, other users pulls the changes but they dont need to decrypt anything until they need to use the keys. So it's just gpg-encrypted data atop of a git repository (one can think of a |