Stuck behind a firewall?

For those behind firewalls who block outbound SSH connections, we have now added a workaround for you.

The SSH daemon for pushing Git repositories also now listens on port 443, however we use that port for other things (https traffic) on our main IP, we’ve added ssh.gitorious.org who listens on port 443.

By adding this to your ~/.ssh/config:

Host gitorious.org
    Hostname ssh.gitorious.org
    Port 443

you don’t have to remember to change git@gitorious.org to git@ssh.gitorious.org whenever you copy the push url from the website.

If you’re behind an even stricter firewall you’ll have to setup something like Corkscrew, Tor Arne kindly provides an example config in this mailing list thread. As always, contact support@gitorious.org if you run into any issues.

7 Comments

  1. nelson
    Posted December 1, 2009 at 12:30 pm | Permalink

    These ssh tips should be in the faq…

  2. Raven
    Posted May 20, 2010 at 6:24 pm | Permalink

    You do know that you are promoting people to get fired by their company because that’s a blatant security violations in almost all companies and this is just a lawsuit waiting to happen. Hope your .org organization have money to hire lawyers.

  3. Marius Mathiesen
    Posted May 21, 2010 at 8:31 am | Permalink

    @Raven: Gitorious users should verify that using this approach does not violate security or other policies in the company they are employed by.

    Using port 22 for SSH traffic is only a convention; allowing SSH traffic on other is not a security violation.

    Companies who feel they need stricter control over the traffic sent over their network may use stronger control measures than strictly controlling which ports are open.

    Any user installing and using Corkskrew knows that this is a means of masquerading SSH traffic as HTTP, and should of course verify that this is in accordance with company policy.

  4. Posted July 28, 2010 at 8:29 pm | Permalink

    Thank you for this post! After that I was looking for Thanks!

  5. Posted July 12, 2011 at 5:38 am | Permalink

    Gitorious users should verify that using this approach does not violate security or other policies in the company they are employed by

  6. Posted January 9, 2012 at 9:02 am | Permalink

    Using port 22 for SSH traffic is only a convention; allowing SSH traffic on other is not a security violation.

  7. Posted July 13, 2012 at 2:59 pm | Permalink

    fter 2 months and being stuck with fatal: git-http-push failed I finally found that! and it works fine :)


Follow

Get every new post delivered to your Inbox.

Join 845 other followers

%d bloggers like this: