My company's network is "protected" by a proxy allowing only outgoing HTTP and HTTPS connections.
Since I have a personal server running Linux at home, I want to keep an eye on it... My computer at work is running Windows.
Before I used
Shell-In-A-Box. It is a java applet on the client side, which POSTs the commands to a CGI script located on the server side. It is a bit ugly but... it works ;)
I switched to SSH, thanks again
MichouX!
On my server, I just asked
sshd to listen on port 443 (HTTPS):
...
# What ports, IPs and protocols we listen for
Port 22
Port 443
...
Now on my computer at work, I run
PuTTY (the best SSH client for Windows).
You just need to setup your proxy settings under "Connections - Proxy" with authentication if needed.
Then you connect as usual to your server, just using the 443 port instead of the default 22 port.
This is nicer... but you can do even better: there is an option in good SSH clients to setup tunnels in order to forward ports.
In fact with our opened SSH connection we are now able to forward as much ports as we want and enjoy the real internet: pop3, imap, irc, ICQ/MSN/Yahoo/Jabber, etc.
You can forward ports manually or if your are lazy like me, setup one single port to do dynamic forwarding using SOCKS.
For example in PuTTY I have this:
Then you just need to tell your favorite network applications to use your SOCKS proxy, for example in Thunderbird:
Or in Gaim:
So we now have a full connection to internet, on a network allowing only outgoing HTTP/HTTPS connection through a proxy with an authentication... NICE :)
It is fun to realize the encapsulation of packets and the number of hosts used before "real" internet...
5 commentaire(s)...
