From 20d338536a6421ff1ec359d1098eeed64c7628dc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 24 May 2014 15:28:39 -0400 Subject: [PATCH] update --- ...d_ssh_keys_for_remotes_using_the_standalone_tarball.mdwn | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) 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 index ccec9370f3..8668fed66a 100644 --- 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 @@ -12,4 +12,8 @@ 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. +ssh key when they cannot be. --[[Joey]] + +> After recent sshpassword changes, the webapp sets up a dedicated ssh key +> by default. If the user chooses to use an existing ssh key, it will be +> used. So this is less likely to be a problem. --[[Joey]]