git:// through proxy

I’m behind a firewall that is blocking port 9418 (git) and am trying to install some tools that are explicitly doing a checkout of git://, so I can’t switch to https for the checkout.

So I’m wondering if it’s possible to redirect all traffic to port 9418 through a proxy and if so how 🙂

  • Create new JUnit test and run with git bisect
  • Run brunch build and tests after to push into a git repo
  • Removing patch from Gerrit
  • Git push not appearing in Github
  • Git: Cloning through symlink requires password?
  • Git rebase interactive the last n commits
  • Docker workflow for automated builds on Github-Dockerhub
  • I forked a project, then push some changes, can the project owner see my update?
  • How to make sure teammates don't screw up the git repo by rewriting history?
  • Progress not displayed in Github contribution chart?
  • Egit Eclipse insufficient data written)
  • Collapse git commits after push upstream (github)?
  • 4 Solutions collect form web for “git:// through proxy”

    Have a look at core.gitproxy setting in Git config.

    Quick googling revealed this script that may be useful (or may not — I did not try it):

    If you are talking about git submodules, try this:

    git config --global url. git://

    …taken from here.

    This way, you don’t need to set any proxy, nor run any script.

    Have you tried an ssh-based TCP tunnel? If you have an ssh server that (a) is outside your firewall and (b) allows IP forwarding, you can do:

    ssh -L localhost:9418:<remote>:9418 me@remote-ssh-server

    or, if you have to run sshd on port 443 to get around your firewall,

    ssh -P 443 -L localhost:9418:<remote-host>:9418 me@remote-ssh-server

    Then, locally:

    git checkout git://localhost/...

    Obviously this isn’t transparent, and it’s a little convoluted – there are no doubt tools out there that are more specifically targetted at the problem. However, I typically use this method because it uses tools I have to hand (ssh and a cheapo virtual server I rent).

    (I’ve actually never tried this with a git connection, but I see no reason why it wouldn’t work. I’ve used it with many other single-TCP-port protocols without problem.)

    You need to make core.gitProxy point to a proxy command that will connect git to the remote server through your SOCKS proxy. You can create a script with the following content to serve as a proxy command:

    nc -x <your_proxy_host>:<your_proxy_port> $1 $2

    The two parameters, representing the remote host and port, will be passed to the proxy command by git. If you name this script git-proxy and make it accessible from your $PATH, you can call git config to set it:

    git config --global --add core.gitProxy git-proxy
    Git Baby is a git and github fan, let's start git clone.