git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Bill Lear" <rael@zopyra.com>
Cc: "Julian Phillips" <julian@quantumfyre.co.uk>, git@vger.kernel.org
Subject: Re: git protocol over port-forwarding
Date: Thu, 15 Mar 2007 11:14:37 +1300	[thread overview]
Message-ID: <46a038f90703141514q5273e493r87f0ac7f52c1c216@mail.gmail.com> (raw)
In-Reply-To: <17912.29057.435478.123662@lisa.zopyra.com>

On 3/15/07, Bill Lear <rael@zopyra.com> wrote:
> On Wednesday, March 14, 2007 at 21:05:37 (+0000) Julian Phillips writes:
> >...
> >I don't think there is anything that needs changing with the git daemon
> >... or at least I was able to successfully clone over an SSH port forward.
> >
> >I did get the same error as you originally, but this was due to SSH
> >failing to setup the tunnel connection (checking the logs showed that I
> >had got the hostname in the forward wrong).
>
> Ok, so were you doing something like this:
>
> % git clone git://localhost:5700/project
>
> etc.?  and not using the ssh protocol, like this:
>
> % git clone ssh://...

I think pure port forwarding won't support git+ssh. For that you need
the proxycommand approach I mentioned. Actually, I think there's a
more elegant approach just saying

Host fooproxied
    ProxyCommand ssh -q -a foo.yourdomain nc -q0 %h 22

cheers,



m

  reply	other threads:[~2007-03-14 22:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 18:37 git protocol over port-forwarding Bill Lear
2007-03-14 21:05 ` Julian Phillips
2007-03-14 22:04   ` Bill Lear
2007-03-14 22:14     ` Martin Langhoff [this message]
2007-03-14 23:14       ` Jakub Narebski
2007-03-15  0:33         ` Bill Lear
2007-03-15  1:32           ` Bill Lear
2007-03-15  4:29         ` Martin Langhoff
2007-03-14 22:30     ` Julian Phillips
2007-03-14 21:07 ` Martin Langhoff

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=46a038f90703141514q5273e493r87f0ac7f52c1c216@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    --cc=rael@zopyra.com \
    /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;
as well as URLs for NNTP newsgroup(s).