git-annex/doc/design/encryption/comment_4_8f3ba3e504b058791fc6e6f9c38154cf._comment
http://joey.kitenet.net/ 36894655f3 Added a comment
2011-04-07 19:59:30 +00:00

10 lines
672 B
Text

[[!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.
"""]]