summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar gavinwahl@d3a94ffbd6df3b8833a53ff11ec435f58f7c44a9 <gavinwahl@web>2016-04-03 03:43:58 +0000
committerGravatar admin <admin@branchable.com>2016-04-03 03:43:58 +0000
commit4dd277f449d35d5e4c568b1ce2bc1b0a3c385c43 (patch)
treedc8ceb21599657bd04eb5f82b292521e7b789583
parent1c0b317d80126b52d7c0e0622b9c0894f2f17094 (diff)
Added a comment: Shared key - how many keys?
-rw-r--r--doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment b/doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment
new file mode 100644
index 000000000..ee4c2f328
--- /dev/null
+++ b/doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="gavinwahl@d3a94ffbd6df3b8833a53ff11ec435f58f7c44a9"
+ nickname="gavinwahl"
+ subject="Shared key - how many keys?"
+ date="2016-04-03T03:43:58Z"
+ content="""
+In shared mode, is a single key used to encrypt every file in the repository? Or is a new key created for each file?
+
+Shared mode has the properties I need - getting access to the git repo should give you access to all the content. BUT, if one loses access to updates to the git repo, they should not have access to files added after they lost access.
+"""]]