From 974be83aef8a25c6e12aabea5bf1efdb9c95856e Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnWhpB2MotO7nq1-RdOGd_WuxzDNlwthMQ" Date: Thu, 4 Sep 2014 17:44:48 +0000 Subject: [PATCH] --- doc/forum/Creating_a_more_secure_shared_encryption.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/forum/Creating_a_more_secure_shared_encryption.mdwn diff --git a/doc/forum/Creating_a_more_secure_shared_encryption.mdwn b/doc/forum/Creating_a_more_secure_shared_encryption.mdwn new file mode 100644 index 0000000000..5b2019f37c --- /dev/null +++ b/doc/forum/Creating_a_more_secure_shared_encryption.mdwn @@ -0,0 +1,7 @@ +I was wondering if there was a way to make shared encryption more secure. Here is my suggestion: +The shared repository is encrypted using a key for the whole repository, just the way normal encryption would work. +The server additionally keeps a copy of every user's public key. +When a user is authorized, their repository is initialized and they receive the common key, encrypted by their public key. +The only issue would be storage of the common key, which would have to be restricted to repository on a trusted machine. + +Not sure if this would be easy for you to implement, but I figured I'd submit a post detailing it, to see if maybe it was doable.