diff options
| -rw-r--r-- | doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_1_9523af238c6cd2ab66f83474dd580427._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_1_9523af238c6cd2ab66f83474dd580427._comment b/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_1_9523af238c6cd2ab66f83474dd580427._comment new file mode 100644 index 000000000..9d567f376 --- /dev/null +++ b/doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_1_9523af238c6cd2ab66f83474dd580427._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-03-07T19:46:27Z" + content=""" +A rsync special remote needs ssh to run rsync --server, +you have it running git-annex-shell. + +That can't work. It is possible to lock down generic rsync over +ssh to only operate in one directory, but git-annex-shell +is not the tool to do it. + +If there's a bug here, it's whatever led you to expect this would work.. + +(But, if you make a gcrypt special remote, git-annex-shell can be used +to access it, and it'll be all encrypted and files stored with rsync, +and can be locked down.) +"""]] |