summaryrefslogtreecommitdiff
path: root/index.mdwn
diff options
context:
space:
mode:
authorrhatto <rhatto@ratatosk.fluxo.info>2014-03-14 15:03:43 -0300
committerrhatto <rhatto@ratatosk.fluxo.info>2014-03-14 15:03:43 -0300
commitb5378493968b2ed72f3b5f0d38377afc0b0049cd (patch)
tree5bdafe495ec1fbebc995c1d3950b5cc3d0eb13e3 /index.mdwn
parent23b810b99f9db4d058b6d75fae2504767f23bfac (diff)
downloadkeyringer-b5378493968b2ed72f3b5f0d38377afc0b0049cd.tar.gz
keyringer-b5378493968b2ed72f3b5f0d38377afc0b0049cd.tar.bz2
Minor doc change 3 (gitolite test)
Diffstat (limited to 'index.mdwn')
-rw-r--r--index.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/index.mdwn b/index.mdwn
index 4b82085..23a70e5 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -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.