diff options
| author |  http://joey.kitenet.net/ <joey@web> | 2011-04-07 19:59:30 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-04-07 19:59:30 +0000 |
| commit | 36894655f34eb46b386f708b889f05ffd269f0cf (patch) | |
| tree | 69c2055a49af7f0cfa6d9f81b91469ed9dc94b78 /doc/design | |
| parent | 17e974d32d956fd99416da706e7ae008ed7af308 (diff) | |
Added a comment
Diffstat (limited to 'doc/design')
| -rw-r--r-- | doc/design/encryption/comment_4_8f3ba3e504b058791fc6e6f9c38154cf._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/design/encryption/comment_4_8f3ba3e504b058791fc6e6f9c38154cf._comment b/doc/design/encryption/comment_4_8f3ba3e504b058791fc6e6f9c38154cf._comment new file mode 100644 index 000000000..14eb1acac --- /dev/null +++ b/doc/design/encryption/comment_4_8f3ba3e504b058791fc6e6f9c38154cf._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joey.kitenet.net/" + nickname="joey" + subject="comment 4" + date="2011-04-07T19:59:30Z" + content=""" +@Richard the easy way to deal with that scenario is to set up a remote that work can access, and only put in it files work should be able to see. Needing to specify which key a file should be encrypted to when putting it in a remote that supported multiple keys would add another level of complexity which that avoids. + +Of course, the right approach is probably to have a separate repository for work. If you don't trust it with seeing file contents, you probably also don't trust it with the contents of your git repository. +"""]] |