diff options
| author | rhatto <rhatto@ratatosk.fluxo.info> | 2014-03-14 15:03:43 -0300 |
|---|---|---|
| committer | rhatto <rhatto@ratatosk.fluxo.info> | 2014-03-14 15:03:43 -0300 |
| commit | b5378493968b2ed72f3b5f0d38377afc0b0049cd (patch) | |
| tree | 5bdafe495ec1fbebc995c1d3950b5cc3d0eb13e3 | |
| parent | 23b810b99f9db4d058b6d75fae2504767f23bfac (diff) | |
| download | keyringer-b5378493968b2ed72f3b5f0d38377afc0b0049cd.tar.gz keyringer-b5378493968b2ed72f3b5f0d38377afc0b0049cd.tar.bz2 | |
Minor doc change 3 (gitolite test)
| -rw-r--r-- | index.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -189,8 +189,8 @@ With theses scripts, the workflow is more or less like this: - 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 -kind of distributed encrypted filesystem). +In summary, keyringer data store is basically gpg-encrypted data atop of a git +repository (one can think of a kind of distributed encrypted filesystem). Git was chosen to host encrypted info mostly for two reasos: easy to distribute and its the only VCS known to make easier repository history manipulation. |