Dec 032012
 


So you’re on the road. Being the road warrior you are, you can appreciate the finer things in live. For example some privacy while surfing the web (never heard of that anyway, but lets continue). Be it in a boring hotel room, a local coffee bar, or some other place connected through the Internet by means of WiFi. Using an WiFi encryption will probably make your browsing session a private one from “strangers” who are trying to eavesdrop on you, but if the know the pre-shared-key (WEP/WPA) the can still with a little bit of trouble read your data/information! And none the less, the proprietor of the gateway/router is often still in the position to eavesdrop on all the websites (and content) of websites you’re visiting.

Even if you’re visiting an SSL website they still can see “which” website you’re visiting. From there on everything is encrypted (including the URL’s, payload, etc).

There’s this magnificent little 444KB program called putty.exe . Mostly you use it to connect from a Windows PC to a (distanced) server running an SSH daemon to manage the hosts. Nobody can eavesdrop on you because it’s completely encrypted. Butt this program has some really nice/crazy features. It can act as you local (HTTP) socks proxyserver when you’re on the road.
Continue reading »

Mar 192012
 

putty_ssh_proxy_error_403I was trying to setup (SSH) Internet access to github.com on some servers wich don’t have any Internet connectivity.

I wanted to use SSH instead of HTTP because this way you can use encryption keys instead of username and password authentication for github.

There are some excellent guides out there how to do this with corkscrew. I used one of those and almost got it working …… :
[martin@dhcp3b.hgl-pv ~]$ corkscrew 10.255.248.131 8080 github.com 22
Proxy could not open connnection to github.com: Forbidden

putty displayed the same error so the problem was probably with the proxy. If you need to fix this allow the (Squid) proxy to be able to open a connection to port 22.

Continue reading »