begin quoting Bob La Quey as of Thu, Aug 21, 2008 at 02:18:00PM -0700: > On Thu, Aug 21, 2008 at 1:13 PM, SJS <[EMAIL PROTECTED]> wrote: > > 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. > > I do not know much about ssh. I am running a client application from > my laptop. Does that mean I
Do you control the server you're trying to log in to? Or, really, any server under your control that you could ssh _through_? You can easily run sshd on whatever port you desire. Port 80 even. [snip] > > 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. > > I am traveling. I use public libraries and Internet cafes. Mostly it > just works, but sometimes like today, public library branch in Pine > Valley I cannot use ssh directly. I'd certainly raise the issue with them, just so there's a complaint in the system. No reason a library shouldn't open up port 22. That doesn't help *today*, alas. Unless they have a tech-minded person on-site. I wonder what happens when you try to hit a page on a server that's listening on, oh, port 8080? > Nice surroundings though. There is that. -- I should set up an sshd on port 443 sometime, just in case. Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
