But port 443, which is normally the HTTPS port, often works, because SSH and HTTPS look a lot like each other to filtering software, so your SSH session will look like an HTTPS session. Port 80 is unlikely to work, because most places that have firewalls analyse the traffic on that port and block anything that isn't HTTP. If the firewall lets you, you can run ssh to any port, but that requires the ssh server to be listening on that port. In short, it might just be safer to talk to them. If they've got a reason for blocking ssh, it's likely they'll view any extreme attempts to circumvent it fairly negatively. You need to do something and they're stopping you. You might just want to have a word with your network admins.

This should skirt around the firewall problem completely because it all happens on Port 80 but it will require you to be running Apache and set up a number of things:Ī VPN might be an option but if ssh is locked out, I'd expect that to be excluded too. Your bzr path would then look something like: bzr+ssh://host:80/path/Īnother method is to use WebDav. You'll need to edit /etc/ssh/sshd_config and change Port to 80. Warning If you have something else running on port 80 (on the server) this will not work and will likely mean you completely lose SSH access to the server! If you have control over the server, and still want to try it, you can change the sshd port to port 80. A good corporate firewall will inspect traffic regardless of port so changing port just might not work.

Download ssh tunnel manager for ubuntu