mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Browse source
This commit is contained in:
https://me.yahoo.com/a/lgHmyxsDhPHsmhHSpL5vMyo8qOUwu4WiaNog#8cc41 2014-11-11 10:16:31 +00:00 • committed by admin
parent df234eec07
commit 63c14e73c5
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/forum/Shared_Encryption_does_not_Work_as_Expected.mdwn Normal file
View file

@ -0,0 +1,11 @@
I recently started to set up a share that would be synced between multiple machines. Since I control all of them I thought it might be cool to try using the suggested "shared encryption". This seems to have been a mistake.
My project folder is now a big mess of symlinks to read-only files.
I can fix this with a "cp -RH" and get my data back and I can muddle through fixing the permissions but this leads me to two conclusions:
1. I did something wrong but I don't know what. Should I have created the ssh remote first and the local repo second?
2. This feature should either be hidden or the UI should be much more explicit about how to use it properly. This cost me quite a bit of time and frustration.
I really like git-annex so I would appreciate any comments or suggestions.