diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-04-07 22:05:03 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-04-07 22:05:03 -0400 |
| commit | dfc1bfcc76036549eb49d8e88136d9d40e77a51a (patch) | |
| tree | 476dce1647e1a0a74790c6cee2c829ee7508763a /doc/design | |
| parent | e2404ca40933ccdc046d08f7040b2d86e32d5f88 (diff) | |
| parent | c1c470228f24abf6c6b3507268d130df34b876ec (diff) | |
Merge remote-tracking branch 'branchable/master'
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. +"""]] |