Replies

I think this would could be a cool computer security thread demonstrating how to avoid prying eyes or to access freerepublic.com in environments that restrict access.

We Replaced Patrick Leahy's Brains With Folger's Crystals. Let's See If Anyone Notices!

Donate Here By Secure Server

Or mail checks to
FreeRepublic , LLC
PO BOX 9771
FRESNO, CA 93794

or you can use

PayPal at Jimrob@psnw.com

STOP BY AND BUMP THE FUNDRAISER THREAD

Your descriptions of your chain left me a little confused, so rather than try to debug, let me describe what I have done in the past.

First, set up the web proxy on your home system, listening on whatever port you like (8080 is reasonable). The proxy should accept connections only from the localhost.

Second, install an sshd daemon on your home system (and configure it so that you can authenticate yourself when connecting from work).

Then, your ssh client at work should redirect a local port to a remote one -- that is, localhost:8080 to your.home.box:8080. Then connections to localhost:8080 will be forwarded through the ssh tunnel on to your home system's port 8080.

Your web browser at work should use 127.0.0.1:8080 as the proxy.

Personally, the way I like to do it, is to run the Junkbuster proxy at home, which forwards requests to a squid cache at home, which forwards requests over an ssh tunnel to anonymizer.com's web proxy. Then, using ssh tunneling I expose my the Junkbuster on my home box to work (workbox:8080 to homebox:8080). It works well.

Do I need an ssh server on my home box to authenticate to before I can access the ssh port forwarding?

I'm pretty sure you do. I haven't used Putty, but I've done similar things with Unix. This is how I set up an encrypted tunnel to use VNC (remote display/control) on my home computer while at work:

Run an ssh server (port 22) and VNC server (port 5901) on my home machine.
On my work machine, I set up the tunnel with this command: "ssh -L 5901:127.0.0.1:5901 [home ip address] sleep 99999". This will establish an ssh connection to my home machine (and ask for my password) which will stay open as long as the "sleep 99999" command is running (which is just a do-nothing program that runs for 99999 seconds). Once the connection is established, my work machine will listen on port 5901 and forward all data received through the ssh connection and to port 5901 on my home machine.
I can now run the VNC client on my work machine by connecting to port 5901 on 127.0.0.1 (which is transparently redirected home).

Hopefully this makes some amount of sense...

A possibility that your corporate firewall is blocking port 5000?

One of my employers was blocking port 22 but allowing port 23 (stupid) so I set up an SSH server on port 23 at home. I built a Linux box at work which woke up periodically (via cron) and connected to the box at home (via private key) and forwarded certain ports over. Here is the script which ran on the box:


/usr/local/bin/ssh2 -q -f -p 23 \
 -L 5801:192.168.50.161:5801 \
 -L 5901:192.168.50.161:5901 \
 -L 222:127.0.0.1:22 \
 -L 8000:127.0.0.1:8000 \
 -L 8001:192.168.50.163:8001 \
 -L 8002:127.0.0.1:8001 \
 -R 5000:147.210.174.52:80 \
 -R 5001:147.210.174.46:80 \
 -R 5002:147.210.174.47:80 \
 -R 5003:147.210.174.48:80 \
 -R 5004:10.103.4.37:80 \
 -R 5005:10.103.4.30:23 \
 -R 513:10.101.4.15:513 \
 -R 222:127.0.0.1:22 \
 -R 322:10.103.4.37:22 \
 tech.junk.net

Using this, I could get into my network services at home from the office, AND contact stuff at work from my machines at home. Worked flawlessly and undetected for years.

Test which ports you can get through the firewall, and read up on SSH port forwarding. You should be able to get it working without too much trouble.

Ever heard of "Bouncer"? Try here

PING