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

response

Browse source
This commit is contained in:
Joey Hess 2018-03-07 15:54:07 -04:00
parent 0a294900b5
commit a1a8b78b88
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/GIT__95__ANNEX__95__SHELL__95__DIRECTORY_won__39__t_match/comment_1_9523af238c6cd2ab66f83474dd580427._comment Normal file
View file

@ -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.)
"""]]