diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawnWhpB2MotO7nq1-RdOGd_WuxzDNlwthMQ <NP@web> | 2014-09-04 17:44:48 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-09-04 17:44:48 +0000 |
| commit | 5bdde8952cf10db2c9f172ade0febed453b7ed6f (patch) | |
| tree | 9b1c5eea650b35ae984eef213d514a13b817dfba | |
| parent | aa29484cded39eddc4920d9f6cc1dd36ee9f2faa (diff) | |
| -rw-r--r-- | doc/forum/Creating_a_more_secure_shared_encryption.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
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 000000000..5b2019f37 --- /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. |