> I'd go for an stunnel setup. You can tunnel any TCP traffic over SSL > (including e.g. ssh-- I've done it), and access to port 443 is just about > guaranteed.
Or, you can just have your ssh server listen on port 443. The only way this wouldn't work is if either (1) port 443 is blocked, which is extremely unlikely; or (2) you're behind an application firewall that detects and blocks non-SSL traffic-- also extremely unlikely. Even the firewall at the agency where I work, which blocks non-HTTP traffic to port 80, doesn't do that. Good luck, A. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
