Re: [PATCH] connect.c: Tell *PLink to always use ssh protocol

2013-03-09 Thread Sven Strickroth
Am 07.02.2013 00:22 schrieb Jeff King:
 On Wed, Feb 06, 2013 at 10:58:49PM +0100, Sven Strickroth wrote:
 
 Default values for *plink can be set using PuTTY. If a user makes
 telnet the default in PuTTY this breaks ssh clones in git.

 Since git clones of the type user@host:path use ssh, tell *plink
 to use ssh and override PuTTY defaults for the protocol to use.

 Signed-off-by: Sven Strickroth em...@cs-ware.de
 
 Makes sense to me, though I'd expect to see this cc'd to the msysgit
 list (which I'm doing on this response) for comment from people who
 might be more familiar with the area.

The msysgit people have a git-wrapper which already enables this (see
https://github.com/msysgit/msysgit/blob/master/src/git-wrapper/git-wrapper.c#L62).

-- 
Best regards,
 Sven Strickroth
 PGP key id F5A9D4C4 @ any key-server
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] connect.c: Tell *PLink to always use ssh protocol

2013-02-07 Thread Sven Strickroth
Am 07.02.2013 00:22 schrieb Jeff King:
 On Wed, Feb 06, 2013 at 10:58:49PM +0100, Sven Strickroth wrote:
 
 Default values for *plink can be set using PuTTY. If a user makes
 telnet the default in PuTTY this breaks ssh clones in git.

 Since git clones of the type user@host:path use ssh, tell *plink
 to use ssh and override PuTTY defaults for the protocol to use.
 ---
  connect.c | 2 ++
  1 file changed, 2 insertions(+)

 diff --git a/connect.c b/connect.c
 index 49e56ba..d337b6f 100644
 --- a/connect.c
 +++ b/connect.c
 @@ -625,6 +625,8 @@ struct child_process *git_connect(int fd[2], const char 
 *url_orig,
  if (!ssh) ssh = ssh;
  
  *arg++ = ssh;
 +if (putty)
 +*arg++ = -ssh;
  if (putty  !strcasestr(ssh, tortoiseplink))
  *arg++ = -batch;
  if (port) {

Just for the completeness: This might have an unwanted side effect...
Using the -ssh parameter sets the protocol to ssh AND the port number to
22. This might break a setting where a user stores a PuTTY default for
ssh, but with a different port number (e.g. because a user always pushes
to a remote ssh repository which resides on a different port).

PuTTY settings for a named session still work, it only affects the
Default Settings session - so users can set up specific sessons in
PuTTY if he wants to change the default port.

-- 
Best regards,
 Sven Strickroth
 PGP key id F5A9D4C4 @ any key-server
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] connect.c: Tell *PLink to always use ssh protocol

2013-02-06 Thread Jeff King
On Wed, Feb 06, 2013 at 10:58:49PM +0100, Sven Strickroth wrote:

 Default values for *plink can be set using PuTTY. If a user makes
 telnet the default in PuTTY this breaks ssh clones in git.
 
 Since git clones of the type user@host:path use ssh, tell *plink
 to use ssh and override PuTTY defaults for the protocol to use.
 
 Signed-off-by: Sven Strickroth em...@cs-ware.de

Makes sense to me, though I'd expect to see this cc'd to the msysgit
list (which I'm doing on this response) for comment from people who
might be more familiar with the area.

Quoted patch follows.

-Peff

 ---
  connect.c | 2 ++
  1 file changed, 2 insertions(+)
 
 diff --git a/connect.c b/connect.c
 index 49e56ba..d337b6f 100644
 --- a/connect.c
 +++ b/connect.c
 @@ -625,6 +625,8 @@ struct child_process *git_connect(int fd[2], const char 
 *url_orig,
   if (!ssh) ssh = ssh;
  
   *arg++ = ssh;
 + if (putty)
 + *arg++ = -ssh;
   if (putty  !strcasestr(ssh, tortoiseplink))
   *arg++ = -batch;
   if (port) {
 -- 
 Best regards,
  Sven Strickroth
  PGP key id F5A9D4C4 @ any key-server
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html