How to Bypass Most Firewall Restrictions and Access the Internet Privately

How to Bypass Most Firewall Restrictions and Access the Internet Privately

aka The Surf At Work Page

For the geeks out there who knows what SSH means and more importantly cares.

Version 2

Created: 10/25/2002 Last Updated: 03/03/2005

Visit the Surf At Work Forums for Questions, Comments, Help, etc!


* Introduction
* Overview
* Audience
* Prerequisites
* When won’t this work?
* Addresses
* Software
* Install the SSH Server
* Configure Windows
* Configure the SSH Server
* Starting/Stoping the SSH Server

* If you have a wired or wireless router at home (Linksys, D-Link, Netgear, etc)
* Setup Putty at Work/School
* Create your tunnel
* For Advanced Users
* Configure Internet Explorer
* Configuring other applications to use the private connection
* Protect yourself from someone looking over your shoulder
* Other firewall & privacy products to try
* Copyright and Disclaimer
* Notes
* Forums

More and more employers and universities are becoming aware of the amount of time their employees or students are spending using the Internet for personal reasons. Obviously employers want to discourage this behavior and may implement a number of different ways to do so. These can include;

* Restricting people from installing programs on their workstation. This usually won’t stop someone from accessing websites, but it may keep people from playing games or using instant messaging software.
* Using a firewall or proxy server to restrict access to websites or other Internet protocols. All your Internet communication passes through your network’s firewall, so it’s a great place to monitor and restrict access. How complex or restrictive it is largely depends how tech savvy your IT department is.
* Using a network monitoring system to “spy” on Internet access. This is a form of firewall monitoring, where your employer can intercept and read/save anything flowing through their firewall. Your IT department may call this an Intrusion Detection System, which is primarily used to monitor for attempted hacker attacks or viruses.
* Installing programs on workstations that monitor Internet access. This is probably the toughest thing to get around because there are so many different vendors that offer this type of software. In addition, there is software that simply records every keystroke you press. In most cases, there’s no way around this other than disabling the software.

This guide discusses a way an employee or student can securely access the Internet while at work or school, and also get around some common firewall restrictions that prevent you from using most networked programs. My definition of “securely” means that there should be no mean by which your employer can know which websites you have visited or are currently visiting, and can not view or decipher the content of those sites (without actually standing over your shoulder.)

Keep in mind that the method I discuss here will protected you from NETWORK monitoring, not actual computer or keystroke monitoring. So if your IT department has some security software installed on your PC, you probably shouldn’t even be looking at this page.

In addition to protecting you from network monitoring, this method can be used to get around a number of other security protections that may be in place;

* Your employer or school allows access to most of the Internet but blocks certain websites that they consider non-work related. Using this method you can access them.
* Your employer or school blocks you from chatting at work using AIM or ICQ or similar instant messaging programs. Follow my instructions and you may be able to get around the firewall and chat at work.
* You want to access your employer or school’s Intranet from home. Setup the shunnel in the reverse order as I describe, with the SSH server on your work computer, and Putty at home. You’ll may be able to access Intranet websites from home just like you were sitting at your work computer.

This is version 2 of the Surf At Work guide. This version details how to encrypt your network traffic using an SSH tunnel with Dynamic Forwarding. Version 1 of the guide was similar, but in addition to SSH used an Apache HTTP Proxy server. The addition of Dynamic Forwarding in Putty removed the need for an external proxy server, assuming your applications can use a SOCKS proxy instead of an HTTP proxy. The old version is still available here for reference.

Using this method will actually allow you to do more than just surf the web privately. You can bypass a firewall and encrypt the network traffic of any program that can use SOCKS proxy. This includes most instant messaging software like AIM, Yahoo!, MSN, IRC, mIRC and others.

Note 03/03/2005
There is little problem with this “newer” method that uses a SOCKS proxy. Some people may consider it a security issue or prevent them from using this. The problem with using SOCKS is that your domain name looks are still done locally (at work) using local DNS servers. So, if your company doesn’t have external DNS, domain names won’t work. They could also theoretically track your browsing by logging DNS requests. So if these seem like a problem to you, use How to Surf At Work Version 1. It does not have this problem because it sets up an HTTP proxy. In that scenario, the DNS looks are done on the proxy machine, not locally.

The objective is to encrypt your network traffic so it can not be read as it passes through over employer or school’s network. To do this, we will;

* Run an SSH server on your computer at home.
* Use an SSH client on your computer at work to create a secure tunnel between your home and work computers.
* Enable Dynamic Forwarding in the SSH client to simulate a SOCKS Proxy.
* Configure Internet Explorer to use a SOCKS Proxy for network traffic instead of connecting directly.

After this is all setup, the process for browsing a website will be as follows. Internet Explorer at work connects to the SSH client running on your computer at work. The SSH client connects to the SSH server running on your computer at home. Internet Exlorer will make requests for websites using the SOCKS protocol, which SSH will intercept and handle for you. Thus, the SSH server talks to the website and returns the web page to the SSH client. The SSH client returns the web page to Internet Explorer.

In essence, you are tricking Internet Explorer into thinking you have a proxy server running on your local machine, when in fact the proxy is running on your computer at home. Since all communication over your work network takes place through SSH, it can not be read. The SSH traffic CAN be seen or detected, but it will look like a garbled mess of letters and numbers. Other than being a little slower than usual, you shouldn’t notice any difference when surfing the web when using the secure method.

Some people that are familiar with SSH and may be asking, “How can Internet Explorer talk to SSH?”. Well, SSH has a great little function called Connection Forwarding. You setup SSH to accept TCP connections on a port and forward them to a port on another computer. SSH takes ALL the network traffic on that port, wraps it in a secure package, and forwards it somewhere else. I refer to this as a “shunnel”; a secure tunnel.

The other trick to this setup is the Dynamic Port Forwarding. Newer versions of SSH can emulate a SOCKS proxy server. A SOCKS Proxy server is a server that acts like a “middleman.” It accepts requests from a client, and connects to the target server on your behalf. Take a look at these links on Webopedia for a little more information; SOCKS Proxy

Shunnel Graphic
This guide is written for a moderately skilled computer user. You MUST know how to install programs on your computer, how to navigate file systems, and how to edit configuration files. A knowledge of “how the Internet works”, like TCP, sockets, ports, HTTP, and other network protocols would be extremely helpful.

To use this method, you need the following;

* A decent computer at home that you can leave connected to the Internet all day while you’re at work.
* A fast Internet connection at home; usually cable or DSL. (Technically, this can work with a dialup modem connection, but it may cause problems and it’s really slow.)
* Microsoft Windows NT, 2000, or XP installed on your computer at home and any flavor of Windows on your computer at work. You may be able to get this to work with 95, 98, or ME, but I can’t say for sure. You definitely can get this to work with Linux or Unix. I don’t know about Macintosh.

When won’t this work?
Please notice the title of this page starts “How To Bypass Most Firewall Restrictions… I say most because the method I describe here will not work for everyone, even if you meet the pre-requisites above. If any of the following are true for you, you probably can’t use this method successfully;

* You can not access any external Internet websites; only internal websites or none at all.
* You can access a few specific Internet websites, but no others at all.

If either of the 2 lines above apply to you, your network administrator is working hard because they are using a “pessimistic” blocking strategy. In other words, they have decided to block everything, and probably only allow specific access. The problem with that strategy however, is that it requires much more work and maintenance than using an “optimistic” strategy, in which they allow access to everything and block only certain “things”.

The method I describe on this page will not work with a pessimistic blocking strategy because it depends on being able to access your home computer from work. 9 times of 10, if you can’t get to, you won’t be able to your home computer either. If for some reason you CAN access your home computer, then great.. proceed If not, you may want to talk to your network administrator. Ask him if they would punch a hole in the firewall so you can SSH to your computer at home. Or come up with some excuse to get access to 1 port on your home computer, then run the SSH server on that port.

Or… maybe you ARE the network administrator and are just curious about how this works. 🙂

Before we start installing and configuring software, you need to find out the following things;

* Your home IP Address
* Your work/school external IP Address

The easiest way to get your IP Addresses is to go to at home and at work. Write down the numbers.

We’re going to be using 2 fairly simple pieces of software; an SSH Server and an SSH Client.

There are a few flavors of SSH Server’s out there, but we’re going to be using OpenSSH because it’s free. The website for OpenSSH is . But wait! OpenSSH doesn’t run on Windows unfortunately… But there is a site that converted OpenSSH to run on Windows, which is what we want! .

Download OpenSSH for Windows from . The version I wrote this document using was 3.7.1p1-1. The latest version should work for you, plus it will have less security holes.

For the SSH Client I recommend using Putty. Putty is a small single executable SSH client with the ability to setup a tunnel. The newer version also support Dynamic Forwarding, which is essential. It’s possible to use OpenSSH as your client as well as your server, but Putty is much easier to setup and use. Download putty.exe from .

Install the SSH Server
The OpenSSH installer comes in a zip file. Unzip the file, then run setupssh.exe. Choose to install both the Client and the Server. It will ask you to install into C:Program FilesOpenSSH. If you choose to install into a different location, that fine, but be aware I will use the above path in this document.

Configure Windows
OpenSSH for Windows uses Windows’ user database for login authentication. That mean you must have a User name and Password setup to login to your home computer. If you don’t, you have 2 choices. 1, set a password on your Windows account, or 2, create a new local account that you will use to login from SSH. I know a lot of people out there don’t use logins or passwords on their home computer, but if you’re using NT, 2000, or XP, the functionality is there, even if you don’t use it.

There are many different flavors of Windows, with different methods of creating a local user. There’s no way I can cover all of them, but here are a few examples;

To create a new account on your home machine (Windows XP):

* Start Menu, open Control Panel, then User Accounts.
* Click Advanced tab, then the Advanced button.
* Highlight Users, then click Actions, then New User.
* Enter a User name, and a Password twice. I recommend you use a User name and Password that is different than anything you have ever used at work. Obviously, your employer probably knows your password, so there’s no security if you use the same password at home.
* Deselect User must change password at next logon.
* Check Password never expires.
* Click Create.
* Close the Windows, close Control Panel.

You should now have a new local Windows user on your home machine. Remember the Login name and password for later.

Configure the SSH Server
We want to configure your SSH server to allow access using User name and Passwords, and to listen on port 443 instead of port 22.

Why port 443 instead of port 22? In most cases your employer will block almost all outgoing network ports except for port 80 and port 443, which are the 2 ports that webservers run on. I used to tell people to run SSH on port 80 because that’s the standard webserver port, but now I recommend you run it on 443. Port 443 is used for encrypted websites, which is what your shunnel traffic will look like as it passes through the firewall. If you have trouble on port 443, try it on port 80 instead. If neither work, you’re probably out of luck.

Open Windows Explorer, navigate to C:Program FilesOpenSSHetc. Open the file sshd_config using Wordpad. (That’s sshd_config not ssh_config!)

Change the line

#Port 22


Port 443

Save the file.

Now open a command prompt. Change to C:Program FilesOpenSSHbin. We are going to create a user and group database from your Windows user database. Type the following;

mkgroup -l > ..etcgroup


mkpasswd -l > ..etcpasswd

These 2 commands will create group and password files at C:Program FileOpenSSHetc

Start/Stoping the SSH Server
On your home computer, open a command prompt. To start your SSH server, type the following:

net start opensshd

To stop your SSH server, type the following:

net stop opensshd

To make it easy, you can create a .bat file that will this command. If you make a shortcut to the .bat file in your Windows Startup program group, then when you turn on your home computer in the morning, the servers will startup automatically, and be ready for you when you get to work.

If you have a wired or wireless router at home (Linksys, D-Link, Netgear, etc)
Some routers call it port forwarding and others call it virtual servers, but the setup is very similar no matter what brand you use. You will need to configure your router to route port 443 to the computer where you’re running the SSH server. I not going to go into details, but there is usually a browser based interface directly to the router, which will have a page to setup virtual servers. Configure it to forward port 443 to your SSH server computer, port 443.

Setup Putty at Work/School
Copy putty.exe to somewhere on your hard drive at work. c: will do fine, or anywhere else you want. Your desktop is convenient but kind of obvious. If you don’t have permissions to write files to your hard drive, just copy putty.exe and shunnel.bat to a floppy disk or burn them onto a CD. Take the disk to work and run Putty from the appropriate drive.

Open Notepad and copy the following into it, change the bold part where necessary;

putty -D 8080 -P 443 -ssh homeIP

* homeIP should be the IP address of your home machine that you wrote down in the Addresses section above.

Save the file as shunnel.bat in the same directory that you saved putty.exe.

Note for advanced users: If your computer at work is already configured to use a proxy server, you need to configure Putty a little differently, but this may still work.

Open Putty in graphical mode, input your connection setting, and also copy the proxy settings from Internet Explorer to Putty’s proxy configuration screen. Putty should now create a secure tunnel through the proxy at work to your computer at home… pretty neat trick.

Create your tunnel
At work, simply double click shunnel.bat to initiate the shunnel. A Putty window will popup asking for a login name and password. Type the user name and password you created above on the Windows account. If it works, you will be presented with a DOS prompt waiting for a command. This is actually a command prompt to your HOME machine. You can use it if you want, but as long as this command prompt is open, your tunnel is alive. To close the tunnel, type exit or close the window.

For Advanced Users
If you are very familiar with SSH and know what you are doing, you can set this up so you don’t have to enter a password each time you create the shunnel. You have to install OpenSSH as your SSH client and then setup key based authentication by creating a public and private key on your work computer. Install the public key on the SSH server on your home computer. Thanks to Robert W. for this suggestion. I may go into more detail on how do set this up in the future.

Configure Internet Explorer
Now we have to configure Internet Explorer at work to use a SOCKS proxy server.

First, at school/work, go to . Write down the number. This is your IP address WITHOUT your shunnel enabled.

In Internet Explorer;

* Open the Tools menu, then click Internet Options.
* Click the Connections tab, then click LAN Settings.
* Check “Use a proxy server …”, then click the Advanced button.
* If “Use the same proxy for all protocols” is checked, uncheck it.
* Delete anything from the “Proxy address to use” and “Port” boxes.
* On the Socks line, enter “” for the address, and “8080” for the Port.
* Click OK a couple times, then close Internet Explorer and restart it.

Proxy Settings Graphic

First go to again. If everything worked correctly, the page should have changed to show your HOME IP address, NOT your work IP address. If it shows your home IP Address, congratulation, your surfing the web securely and privately from work.

Configuring other applications to use the private connection
Most applications that access the Internet can be configure to use the shunnel. For it to work, they have to support a SOCKS 4 or SOCKS 5 proxy connection. Instant messaging programs like AIM, ICQ, Yahoo IM, and mIRC all support this.

Setup is different for all application, but the settings will be the same. You want to configure the application to use a SOCKS 4 or SOCKS 5 proxy server, Host should be, and Port should be 8080.

Protect yourself from someone looking over your shoulder
Here’s a great application that fits in perfectly with the theme of this page. It’s called Ghostzilla; . The idea is that you want to surf the web, but have it look like you are doing normal work to people walking by your computer. Ghostzilla is a browser that hides itself in your normal work applications, like Excel, or Word, or Visual Studio… anything. With a swish of the mouse, Ghostzilla pops up and you can surf the web. If you see someone coming, simply move the mouse away, and it disappears, leaving no trace. Plus, you can easily configure it to use the shunnel as described here, for total privacy!

Other firewall & privacy products to try

Visit the Surf At Work Forums for Questions, Comments, Help, etc!

Copyright 2002-2004 – All rights reserved.
Please do not repost or retransmit the content of this page.
You are welcome and encourged to link to the page.



11/21/2002 – The page is starting to pickup in popularity. I’m interested to know if anyone else has been successfully in getting it to work. Drop me an email. Thanks.

11/21/2002 – Please email me if anyone notices errors or security holes!

01/17/2003 – Changed to use Putty as an SSH Client instead of OpenSSH. Thanks to James.Q.L for this suggestion.

01/22/2003 – Added Ghostzilla blurb.

03/05/2003 – Added Amazon Honor System links to ask for donations. Check it out!

03/19/2003 – Changed theme a bit to highlight ability to bypass a firewall. Based on google searches, getting around a firewall is actually more popular than protecting privacy.

05/22/2003 – Changed recommended SSH port from 80 to 443. Should work just as well on 443 and set off less alarms because traffic on port 443 is encrypted anyway.

06/02/2003 – Chopped page up into “concept” and “description” pages. Now asking for donations to access the description page.

09/11/2003 – Added link to Amazon Wish List

09/13/2003 – Updated Apache instructions to version 2.0.47

09/25/2003 – Updated OpenSSh instructions to version 3.7.1. A security flaw was found in version 3.4 that I was previously using! All users whould upgrade to 3.7.1 or higher.

01/14/2004 – Page resurrected after being down for a few months… Server died, sorry! On temporary hosting until new server is ready.

01/22/2004 – Hosting on rebuilt server.

08/03/2004 – Updated some broken links and changed a few minor wording issues.

08/12/2004 – Major Update! New versions of Putty that support Dynamic Forwarding make Apache unnecessary! I am now calling this page Version 2, which details using Putty and OpenSSH for a SOCKS Proxy via Dynamic Forwarding. The older version, Version 1, that used Putty, OpenSSH, and Apache for an HTTP Proxy can still be found here .

09/26/2004 – Update the “When won’t this work?” section to remove mention of proxy server. Turns out Putty can be setup to create a secure tunnel through a pre-configured proxy server. Also updated the “Setup Putty at Work/School” section to mention the Putty proxy setup option.

03/03/2005 – Added possible security issue note about SOCKS and DNS lookups.

Leave a comment