aboutsummaryrefslogtreecommitdiff
path: root/doc/encryption
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-04-04 14:52:43 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-04-04 14:52:43 -0400
commit3a41c286be3ffec7b6fbb59de2fe5e80d9d28def (patch)
tree121967f2d516f368925384caf8fdd9606f4125a9 /doc/encryption
parent228ccffdacd4386134d20418d173675b3becd85d (diff)
comment
Diffstat (limited to 'doc/encryption')
-rw-r--r--doc/encryption/comment_6_1756ce62906586f876a3491e5d9befde._comment13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/encryption/comment_6_1756ce62906586f876a3491e5d9befde._comment b/doc/encryption/comment_6_1756ce62906586f876a3491e5d9befde._comment
new file mode 100644
index 000000000..81802c625
--- /dev/null
+++ b/doc/encryption/comment_6_1756ce62906586f876a3491e5d9befde._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 6"""
+ date="2016-04-04T18:48:34Z"
+ content="""
+@gavinwahl, it's a single shared key that any clone of the repository
+provides access to.
+
+If you use the [[tahoe]] special remote, storing files in tahoe-lafs does result
+in a new capability (a kind of key) being stored in the git repo.
+So someone with an old clone can't access the files from tahoe-lafs.
+Tahoe is unique in providing that ability.
+"""]]