From 9c41ad3dbc1345bf5138b8c9d80760988fc450d6 Mon Sep 17 00:00:00 2001 From: "gavinwahl@d3a94ffbd6df3b8833a53ff11ec435f58f7c44a9" Date: Sun, 3 Apr 2016 03:43:58 +0000 Subject: [PATCH] Added a comment: Shared key - how many keys? --- ...comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment diff --git a/doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment b/doc/encryption/comment_5_5c9897663aaa83ca39a7e8cb292a3fd1._comment new file mode 100644 index 0000000000..ee4c2f3287 --- /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. +"""]]