View Single Post
  #4  
Old May 6th 05, 03:40 PM
Dylan Smith
external usenet poster
 
Posts: n/a
Default

In article , Paul Tomblin wrote:
"ISP at work"? You've never worked at a company with a real IT
department, have you? Ours doesn't allow anything out of the firewall
without passing through proxies that they can monitor, and that means web
telnet, or ftp only. Not even ssh, which is a royal pain in the ass.


Two words:
HTTP CONNECT

Run your ssh server on port 443. Run a script that contacts the web
proxy and connects to the remote ssh server on port 443, and connect
your ssh client to your script. The proxy can't tell the difference
between ssh and https because of their end-to-end encrypted nature.

If you are using Redmondware, PuTTY will actually do the whole thing for
you.

I used to work for $IT_GIANT, and they didn't filter ssh - it was rather
nice of them.

--
Dylan Smith, Castletown, Isle of Man
Flying: http://www.dylansmith.net
Frontier Elite Universe: http://www.alioth.net
"Maintain thine airspeed, lest the ground come up and smite thee"