From: Junio C Hamano <junkio@cox.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] v2: proxy-command support for git://
Date: Fri, 04 Nov 2005 10:57:13 -0800 [thread overview]
Message-ID: <7v7jbow8ae.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v1x1wz7ae.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 04 Nov 2005 08:50:33 -0800")
Junio C Hamano <junkio@cox.net> writes:
> Paul Collins <paul@briny.ondioline.org> writes:
>
>> Regarding internal vs. external hosts, the proxy command can simply
>> run netcat locally to internal hosts, so perhaps that is sufficient.
>
> I was hoping this to become a bit more generalized mechanism
> than that; for example using outgoing plug over HTTP Connect or
> telnet proxy using tn-gw-nav.
I realize the above does not really convey my real objection.
Your "ssh to the proxy/firewall host and run netcat to the
destination" would not work for me to reach the internal hosts
at all (while it would work for external ones), because my
firewall does not know names of our internal hosts (the same for
using tn-gw-nav to cross http or telnet proxy).
next prev parent reply other threads:[~2005-11-04 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 15:55 [PATCH] RFC: proxy-command support for git:// Paul Collins
2005-11-03 18:54 ` Junio C Hamano
2005-11-03 19:22 ` Linus Torvalds
2005-11-03 20:41 ` Carl Baldwin
2005-11-03 21:31 ` Junio C Hamano
2005-11-04 14:57 ` [PATCH] v2: " Paul Collins
2005-11-04 16:50 ` Junio C Hamano
2005-11-04 18:57 ` Junio C Hamano [this message]
2005-11-04 21:06 ` Paul Collins
2005-11-04 21:42 ` Junio C Hamano
2005-11-04 22:04 ` Paul Collins
2005-11-04 22:15 ` Linus Torvalds
2005-11-19 12:13 ` [PATCH] git-proxy updates Junio C Hamano
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=7v7jbow8ae.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.