You can use any free local port number you want, as long as you remember to use the same one in the ssh invocation and in the web browser. If the site mostly uses relative URL references, then this method should be sufficient.įor both of these solutions, there is nothing special about the port 8080. The downside is that some links might not work if the remote site uses absolute URL references. The benefit of this method is that it leaves the rest of the browser traffic alone. Now if you point your web browser at you should see the contents of as it would appear from the remote host. The alternative method is to use SSH to forward a single port: ssh -L 8080:server-hostname:80 remote-host On the upside, you can access the remote servers with their real host names, and can easily access multiple private sites. One down side of this method is that all other traffic in the web browser will also be going through the SSH connection. HTTPS Everywhere is a Firefox, Chrome, and Opera extension that encrypts your communications with many major websites, making your browsing more secure. Once you are done, set your browser's proxy settings back to normal. You should now be able to access the private web page in the same way you would from the remote host.
Now all pages you load in your web browser will be tunnelled through the SSH connection.
Now go to your browser's proxy settings, and configure it to use a SOCKS proxy with host name 127.0.0.1 and port 8080 (or whatever port you passed to the -D option). Log in to the remote machine using the following command: ssh -D 8080 remote-host There are two ways you can do this with SSH.
0 kommentar(er)
