Merge remote-tracking branch 'branchable/master'
This commit is contained in:
commit
06a0458ec8
2 changed files with 18 additions and 0 deletions
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 3"
|
||||
date="2011-03-30T18:15:18Z"
|
||||
content="""
|
||||
Yes, encrypting the symmetric key with users' regular gpg keys is the plan.
|
||||
|
||||
I don't think that encryption of content in a git annex remote makes much sense; the filenames obviously cannot be encrypted there. It's more likely that the same encryption would get used for a bup remote, or with the [[special_remotes/directory]] remote I threw in today.
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
|
||||
nickname="Richard"
|
||||
subject="comment 4"
|
||||
date="2011-03-30T18:20:56Z"
|
||||
content="""
|
||||
Picking up the automagic encryption idea for annex remotes, this would allow you to host a branchable-esque git-annex hosting service. (Nexenta with ZFS is a cheap and reliable option until btrfs becomes stable in a year or five).
|
||||
"""]]
|
Loading…
Reference in a new issue