Yup, just shape traffic that's unidentifiable (encrypted SSL should be going to port 443 not port 80 and will be differently labelled) between clients and the HTTP-Tunnel server farm by both protocol and destination subnet or indeed domain.
Quote:
|
Also please try to surf our web site via https://www.http-tunnel.com. People have suggested to us that even though their ISPs have blocked http to our servers, secure http is still available. The web page may be available if you try to access it this way, but you will still be unable to use HTTP-Tunnel itself.
|
I see it's gaining notoriety already, quite rightly considering this is a fairly big security risk to some companies and an irritation to ISPs that shape bandwidth, already being blocked by some, interesting. Personally I'd just shape the traffic to the same policies as peer to peer, IMHO this is nothing more than some people trying to make some cash, where anything but port 80 is blocked it's for good reasons, and advertising it as a way around firewall policies and traffic shaping (implicitly) is IMHO out of order.
Hope that answers your question
