From de5f0cc5fb52ab19358c2077dddfb5d39808293f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 27 Dec 2013 14:45:21 -0400 Subject: [PATCH] new bug --- ..._for_remotes_using_the_standalone_tarball.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/assistant_should_set_up_dedicated_ssh_keys_for_remotes_using_the_standalone_tarball.mdwn diff --git a/doc/bugs/assistant_should_set_up_dedicated_ssh_keys_for_remotes_using_the_standalone_tarball.mdwn b/doc/bugs/assistant_should_set_up_dedicated_ssh_keys_for_remotes_using_the_standalone_tarball.mdwn new file mode 100644 index 0000000000..ccec9370f3 --- /dev/null +++ b/doc/bugs/assistant_should_set_up_dedicated_ssh_keys_for_remotes_using_the_standalone_tarball.mdwn @@ -0,0 +1,15 @@ +git remotes that have git-annex and git "installed" using the linux +standalone tarball (or the OSX dmg) may not have git-receive-pack in PATH. + +To make `git annex sync` and `git push` etc work on such a remote, +it needs to have a dedicated ssh key that runs git-annex-shell and uses it +to run the command. + +The assistant sets that up when it sets up a dedicated ssh key. However, if +the server can be sshed into without a password using an existing ssh key, +the assistant re-uses that key. + +The assistant should either always set up a dedicated ssh key, even when +not otherwise needed, or it should probe to see if git-receive-pack and +git-send-pack can be run as part of its probing, and set up a dedicated +ssh key when they cannot be.