From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git protocol over port-forwarding
Date: Thu, 15 Mar 2007 17:29:38 +1300 [thread overview]
Message-ID: <46a038f90703142129q55254a98na3341da0b6a0319b@mail.gmail.com> (raw)
In-Reply-To: <et9vkm$2j4$1@sea.gmane.org>
On 3/15/07, Jakub Narebski <jnareb@gmail.com> wrote:
> I think it could be done but with _two_ port forwarding, one from git
> port to ssh port or 5700 port, on your computer (probably reverse tunnel),
> second from 5700 port to git port... unless you configure git server
> to use different port...
All the protections against man-in-the-middle attacks (host key
verification, etc) prevent straight port forwarding. That's why if you
want git over ssh you have to use the proxycommand option to ssh.
IMHO, YMMV, etc. ;-)
m
next prev parent reply other threads:[~2007-03-15 4:29 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
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 [this message]
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=46a038f90703142129q55254a98na3341da0b6a0319b@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).