From eb50fa086f9258129edbf52a6bcdcdfe3131ae04 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 27 May 2013 19:14:37 +0000 Subject: [PATCH] Added a comment --- ...mment_3_acdbf92f646dbbf691621f08b3d94c26._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Securing_a_shared_ssh_server/comment_3_acdbf92f646dbbf691621f08b3d94c26._comment diff --git a/doc/forum/Securing_a_shared_ssh_server/comment_3_acdbf92f646dbbf691621f08b3d94c26._comment b/doc/forum/Securing_a_shared_ssh_server/comment_3_acdbf92f646dbbf691621f08b3d94c26._comment new file mode 100644 index 0000000000..ea48a2caf0 --- /dev/null +++ b/doc/forum/Securing_a_shared_ssh_server/comment_3_acdbf92f646dbbf691621f08b3d94c26._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 3" + date="2013-05-27T19:14:37Z" + content=""" +I am confident that it will be *easier* to install git-annex-shell on your ssh server than it will be to lock down rsync. + +All you need to do is go get the standalone linux tarball of git-annex, untar it, and add its directory to PATH. + +You can google for perl scripts that lock down rsync, but I have never been happy with any of the ones I found. +"""]]