More to the point: I'm currently working behind a corporate firewall. (Using Xubuntu 10.10, for those interested) and port 22 is one of the blocked ports. Through collaboration between the engineering team and ICS, we have port 22 unblocked for a few specific hosts. One of these is an SSH tunnel we use to remote out to other places.
Contact your local IT department and ask for a specific host to be permitted through the firewall on port 22. Then, if you're using SSH keys to authenticate (which I suggest you do), then all you need to do is enable SSH Agent forwarding in your local SSH configuration. If you want to get real fancy, you can use a tool like corkscrew to auto-tunnel through the proxy without need for typing it all out manually. If you're using a larger webservice, such as Github, chances are they already have another host set up which listens for SSH traffic on an unblocked port. (ssh.github.com listens for SSH traffic on port 443, for instance). If this is all you require, this can save you a lot of nonsense (like purchasing your own VPS to act as proxy). If all of this fails and IT refuses your request, the only thing I can suggest to you is that you wait until you get home to do whatever it was that needed doing. With rare exceptions, there is nothing so overpoweringly urgent that it cannot wait to be SSH'd to and fixed. -- Registered Linux Addict #431495 For Faith and Family! | John 3:16! fsdev.net 0x5f3759df.org -- You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup
