On Wed, Nov 10, 2010 at 12:40 PM, Mac Newbold <[email protected]> wrote: > If they're not doing content filtering, you could also do ssh tunneling > over port 80 or maybe openvpn over port 80, and be able to use their > faster link. That said, some filters watch port 80 for non-http. But if > they allow port 443 for SSL/https, you can easily run openvpn on that port > I bet, as they won't be able to tell one ssl connection from another, and > can't see whether it is http over ssl or vpn over ssl.
And if they put you through a proxy you might be able to use corkscrew - http://www.agroman.net/corkscrew/ - to tunnel your ssh session through their HTTP proxy. Then you use that ssh session as a local SOCKS proxy for your web traffic. Adding a few layers? You betcha! Keeping traffic ssh encrypted over a wireless network, priceless. -- Joseph Scott [email protected] http://josephscott.org/ _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
