RiggsHill Software

Here's the problem: At work there's an internal web server which holds all kinds of info that's not for public eyes but I'm too lazy to drive to work to update logs or to see what's going on, so how to get to the internal server without just blowing a hole in the firewall? PuTTy to the rescue (again). The firewall already has an ssh port forward to the gateway system. Putty allows forwarding a local port to a remote machine:port. So setting a local port (pick a number like 5432) and forwarding it to the internal server:80 sets up the tunnel. In Mozilla, setup a proxy on localhost:5432 and ALL (and I mean all) traffic is routed to the server behind the firewall. Slick. Putty allows for multiple ports - so I forward the standard svn ports at the same time. Then by directing scn to localhost, all traffic is routed automagically to the server behind the firewall.