begin quoting Bob La Quey as of Thu, Aug 21, 2008 at 12:26:54PM -0700: > My problem: I want to use ssh to get at my remote server but I am > behind a firewall that I have no control over. It does allow normal > http service (tcp80) > > One possible solution: > http://dag.wieers.com/howto/ssh-http-tunneling/ > > Anyone else have this problem?
Not in a long time, and even then, running sshd on port 443 worked. > Solutions? SSH over HTTP is an interesting concept, but the underlying premise I have a problem with... WHY did the network security folks (or whoever arranged things so that you'd be behind a firewall) nail down the firewall like that? What are the security threats that they are concerned with, and are your actions in subverting it in violation of the TOS/regulations/rules/contract? It's almost always better to approach the network security folks and ask for an exemption, after demonstrating that you are not an idiot liable to wreak havoc upon the network. Then end result of this sort of restriction will be the white-listing of "acceptable servers", and that would just suck. If it's an ISP, well, take your money somewhere else. If it's "free airport wifi" that you're fighting with, more power to you -- those guys are assholes with delusions of competence. -- "Free" implies a lack of strings. If there are strings, it's "conditional". Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
