Martin Langhoff wrote: > On 3/15/07, Bill Lear <rael@xxxxxxxxxx> 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 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... -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html