This screenshot can be seen in Figure 7.įigure 7: Socks settings for Internet Explorer Once again we’ll use the “localhost” as the host and port 80 for our tunnel. You must then click on the “Advanced” tab to fill out the Socks connection form. Here you will need to check the box that says “Use a proxy server for your LAN”, this screenshot can be seen in Figure 6.įigure 6: Proxy server settings for Inernet Explorer Once again the location of the “Proxy settings” for internet explorer will vary depending upon which version you are running but generally the path is: Tools > Internet Options > Connections tab > LAN settings. The same concept applies when configuring internet explorer. The screen shot of this configuration can be seen in Figure 5.įigure 5: Firefox configuration settins for tunneling HTTP over SSH The port will be port 80 in this case because we told Putty to tunnel our connection via port 80, YMMV (your method may vary). Once there you will need to highlight the “Manual proxy configuration”, then for the “SOCKS Host” use localhost. The actual steps to get to the “Connection Settings” within Firefox may vary depending on which version you’re running but generally the path is: Tools > Options > Advanced Tab > Network Tab > Settings. Now once a successful connection has been made with Putty we need to configure our browser to use the SSH proxy so that all of our HTTP traffic is funneled over our secure connection. A successful connection with Putty can be seen in Figure 4.įigure 4: Successfull connection via Putty If you didn’t input your authentication credentials correctly you will get a message stating so. Once connected the cursor will move down to the next line, this is the normal operation of Putty. Now click open and another window will open asking for authentication credentials on the remote PC. You can see that I have named my session HTTPtunnelViaSSH in Figure 3. Once you have done this you can save your session so that you can easily connect the next time. If this were the case you need to make sure that the remote SSH server is listening on port 443 instead of the default 22. If your organization doesn’t allow communication on port 22 but does allow port 443 simply put 443 in the port form. This could easily be changed to a port of your choosing. You can also see that I am connecting to the remote SSH server on port 22. Once you have set up port forwarding you can then go back to the main “Session” page and type in the IP address of your remote PC. This can be seen in figure 2.įigure 2: Add port and destination settings You will notice that it puts a letter beside the port you have chosen. Once you have done this click the Add button, this will create the forwarded port for the session. A screen shot of this can be seen in Figure 1.įigure 1: Putty port forwarding configuration page You’ll also need to highlight the button that says dynamic. You will also put in the IP address of your remote PC that is running a SSH server. I have chosen to use port 80 as most organizations allow the use of this port. There under the Source port form you will add what port will be doing all of the forwarding. Click on the “Tunnels” tab underneath the branch of “SSH” within Putty. So the first step is to configure Putty for tunneling. For this tutorial I will only focus on Putty. I recommend the Putty client when using XP because it’s free and easy, but you can use any SSH client. Tunneling with Windows XP, IE (internet explorer), Firefox, and Putty (SSH client): In this tutorial we are going to use ports 22 and 80 for our tunneling although you can use any port that is open.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |