Return to Answer

Both putty and openssh support opening a SOCKS proxy. For OpenSSH you'd use:

ssh -D <port> 

And then point your browser at that port. In putty you create a 'dynamic' port forward. You'll find it under the Tunnels menu (sorry, don't have putty on me right at the moment to give you a more detailed location). Enter your desired listening port and then enter anything you like as a destination (it gets ignored for dynamic forwards). You can then point your browsers proxy settings at that localhost:<port> and it should work.

For more information, the relevant part of the putty documentation is at http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter3.html#using-port-forwarding. As others have posted you may not want to circumvent the corporate filtering though as it's not something you may want to explain :).

Edit: As a further note, OpenSSH can be configured to refuse proxying, as you're connecting to your own machine it's unlikely that'll be the case, but it's something to check if you don't manage to get it working.

There are two parts to getting this to work, so I'll address them seperately.

Connecting to your Server:

As you've mentioned that all you can talk to is a proxy on 443 and 80, you'll need to tunnel your SSH connection out through the proxy. You do that by telling Putty to use the proxy server to connect. Under the 'proxy' menu. Select HTTP and then enter the details for the corporate proxy.

From your post, it seems like you've got the connection working fine.

Configure Putty to Create a SOCKS proxy on the local machine

Both putty and OpenSSH support opening a SOCKS proxy. For OpenSSH you'd use:

ssh -D <port> 

And then point your browser at that port. In putty you create a 'dynamic' port forward. You'll find it under the Tunnels menu. Enter your desired listening port and then enter anything you like as a destination (it gets ignored for dynamic forwards). You can then point your browsers proxy settings at that localhost:<port> and it should work.

For more information, the relevant part of the putty documentation is at http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter3.html#using-port-forwarding. 

As others have posted you may not want to circumvent the corporate filtering though as it's not something you may want to explain :).

Both putty and openssh support opening a SOCKS proxy. For OpenSSH you'd use:

ssh -D <port> 

And then point your browser at that port. In putty you create a 'dynamic' port forward. You'll find it under the Forwarding menu (sorry, don't have putty on me right at the moment to give you a more detailed location). Enter your desired listening port and then enter anything you like as a destination (it gets ignored for dynamic forwards). You can then point your browsers proxy settings at that localhost:<port> and it should work.

For more information, the relevant part of the putty documentation is at http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter3.html#using-port-forwarding. As others have posted you may not want to circumvent the corporate filtering though as it's not something you may want to explain :).

Edit: As a further note, OpenSSH can be configured to refuse proxying, as you're connecting to your own machine it's unlikely that'll be the case, but it's something to check if you don't manage to get it working.

Both putty and openssh support opening a SOCKS proxy. For OpenSSH you'd use:

ssh -D <port> 

And then point your browser at that port. In putty you create a 'dynamic' port forward. You'll find it under the Tunnels menu (sorry, don't have putty on me right at the moment to give you a more detailed location). Enter your desired listening port and then enter anything you like as a destination (it gets ignored for dynamic forwards). You can then point your browsers proxy settings at that localhost:<port> and it should work.

For more information, the relevant part of the putty documentation is at http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter3.html#using-port-forwarding. As others have posted you may not want to circumvent the corporate filtering though as it's not something you may want to explain :).

Edit: As a further note, OpenSSH can be configured to refuse proxying, as you're connecting to your own machine it's unlikely that'll be the case, but it's something to check if you don't manage to get it working.

Both putty and openssh support opening a SOCKS proxy. For OpenSSH you'd use:

ssh -D <port> 

And then point your browser at that port. In putty you create a 'dynamic' port forward. You'll find it under the Forwarding menu (sorry, don't have putty on me right at the moment to give you a more detailed location). Enter your desired listening port and then enter anything you like as a destination (it gets ignored for dynamic forwards). You can then point your browsers proxy settings at that localhost:<port> and it should work.

For more information, the relevant part of the putty documentation is at http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter3.html#using-port-forwarding. As others have posted you may not want to circumvent the corporate filtering though as it's not something you may want to explain :).

Both putty and openssh support opening a SOCKS proxy. For OpenSSH you'd use:

ssh -D <port> 

And then point your browser at that port. In putty you create a 'dynamic' port forward. You'll find it under the Forwarding menu (sorry, don't have putty on me right at the moment to give you a more detailed location). Enter your desired listening port and then enter anything you like as a destination (it gets ignored for dynamic forwards). You can then point your browsers proxy settings at that localhost:<port> and it should work.

For more information, the relevant part of the putty documentation is at http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter3.html#using-port-forwarding. As others have posted you may not want to circumvent the corporate filtering though as it's not something you may want to explain :).

Edit: As a further note, OpenSSH can be configured to refuse proxying, as you're connecting to your own machine it's unlikely that'll be the case, but it's something to check if you don't manage to get it working.