The tool needs an update or two regarding a few features (notably it only supports a single tunnel at once), but it pierces through literally any HTTP proxy, since it's really HTTP and not some CONNECT trick over SSL.
Then you just use your favorite OpenVPN over that, and make all traffic (including DNS, and except your httptunnel endpoint) go over it.
Not "literally" any HTTP proxy, as IDS systems have very little trouble distinguishing tunneled traffic from real web sessions. If someone wants to block you, they will. My point was more: If you're going to pick a port other than 22 to avoid networks that block "ssh", 443 is probably the best choice.
The tool needs an update or two regarding a few features (notably it only supports a single tunnel at once), but it pierces through literally any HTTP proxy, since it's really HTTP and not some CONNECT trick over SSL.
Then you just use your favorite OpenVPN over that, and make all traffic (including DNS, and except your httptunnel endpoint) go over it.
[0] http://www.nocrew.org/software/httptunnel.html