Git development
 help / color / mirror / Atom feed
From: Gert Palok <gert_p@ut.ee>
To: git@vger.kernel.org
Subject: git fetch with GIT_SSH fails with "The remote end hung up  unexpectedly"
Date: Fri, 11 Dec 2009 13:57:54 +0200	[thread overview]
Message-ID: <c39db29a0912110357t2390e2bcv4c447e320ea379a4@mail.gmail.com> (raw)

At my work I have to use an intermediate gateway to ssh to the outer
world. I have set up private-public keys to allow easy connection:
ssh gateway ssh user@outside

Now, I want to fetch from outside repo, so I created a GIT_SSH wrapper:

#! /bin/bash

LOG="/path/to/git-ssh-wrapper.
log"
HOST="$1"
COMMAND="$2"

echo host: $HOST >>"$LOG"
echo command: $COMMAND >>"$LOG"
echo exec: ssh gateway ssh "$HOST" $COMMAND >>"$LOG"
ssh gateway ssh "$HOST" $COMMAND

And ran:
$ GIT_SSH="/path/to/git-ssh-wrapper" git clone ssh://user@outside/path/to/repo
Initialized empty Git repository in /path/to/local-repo/.git/
warning: You appear to have cloned an empty repository.
$ fatal: The remote end hung up unexpectedly

And again just to be sure:
$ GIT_SSH="/path/to/git-ssh-wrapper" git fetch origin
$ fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

Now, the log says:
host: user@outside
command: git-upload-pack '/path/to/repo'
exec: ssh gateway ssh user@outside git-upload-pack '/path/to/repo'

When I ran the command from shell I got:
$ "$GIT_SSH" user@outside "git-upload-pack '/path/to/repo'"
0000

And the connection was kept open (waiting for input, got protocol
error after entering something)

Local environment: Windows Vista 32-bit, cygwin 1.7
Local git version (installed by cygwin): 1.6.4.2
Remote git version: 1.6.4.4

What might be the cause(s)? Have there been compatibility breaking
protocol changes between those version?

--
Gert Palok

                 reply	other threads:[~2009-12-11 11:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c39db29a0912110357t2390e2bcv4c447e320ea379a4@mail.gmail.com \
    --to=gert_p@ut.ee \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox