From 52b838d17e16187bc021bcd8fbadfeb9dc1de621 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 4 Apr 2016 15:14:58 -0400 Subject: [PATCH] comment --- ..._cc9a52e1eab1092848cd53a6497a2f2a._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/bugs/git-annex-shell__58___bad_parameters_when_trying_to_configure_a_shell_sandbox/comment_1_cc9a52e1eab1092848cd53a6497a2f2a._comment diff --git a/doc/bugs/git-annex-shell__58___bad_parameters_when_trying_to_configure_a_shell_sandbox/comment_1_cc9a52e1eab1092848cd53a6497a2f2a._comment b/doc/bugs/git-annex-shell__58___bad_parameters_when_trying_to_configure_a_shell_sandbox/comment_1_cc9a52e1eab1092848cd53a6497a2f2a._comment new file mode 100644 index 0000000000..97b7a5ff37 --- /dev/null +++ b/doc/bugs/git-annex-shell__58___bad_parameters_when_trying_to_configure_a_shell_sandbox/comment_1_cc9a52e1eab1092848cd53a6497a2f2a._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-04-04T19:05:22Z" + content=""" +Locking down git-annex-shell should be the same process as locking down +git-shell. It intentionally copies git-shell's behavior to make this as +easy as possible, and to make git-annex-shell a drop-in replacement for +git-shell in things like gitolite. + +I double-checked with this in my `authorized_keys`: + +command="~/.ssh/git-annex-shell" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICfFntnesZcYz2B2T41ay45igfckXRSh5uVffkuCQkLv joey@darkstar + +Which is using the standard git-annex-shell wrapper script. It works. + +I guess you've either made some mistake in your setup, or possibly +`SSH_ORIGINAL_COMMAND` isn't getting set. I don't know why that would +happen, but it should be easy enough to modify your script to test. +Just make it `set -x` .. +"""]]