Tilted Forum Project Discussion Community - View Single Post

ratbastid · 06-12-2005, 10:56 AM

Aha. Now I understand your limitations. Really, no OUTGOING 22? That's surprising. I can totally get blocking incoming port 22 connections (or maybe forwarding them someplace other than to you), but blocking the outgoing port is just harsh. Maybe you've got a friend in IT who can relax that for you?

Okay, well, set up your sshd to run on port 443 and forget about https. Or... Figure out some way to trigger the server to switch what service is running on that port.

Then (and here's the main thing) go download PuTTY. It's a very nice windows freeware app. It lets you specify the port you want to ssh to. Yes that means you have to have it on your desktop rather than pulling your client down from the server, but... Maybe you could stick it on a flash thumb drive or something.

06-12-2005, 10:56 AM	#8 (permalink)
ratbastid Darth Papa Location: Yonder	Aha. Now I understand your limitations. Really, no OUTGOING 22? That's surprising. I can totally get blocking incoming port 22 connections (or maybe forwarding them someplace other than to you), but blocking the outgoing port is just harsh. Maybe you've got a friend in IT who can relax that for you? Okay, well, set up your sshd to run on port 443 and forget about https. Or... Figure out some way to trigger the server to switch what service is running on that port. Then (and here's the main thing) go download PuTTY. It's a very nice windows freeware app. It lets you specify the port you want to ssh to. Yes that means you have to have it on your desktop rather than pulling your client down from the server, but... Maybe you could stick it on a flash thumb drive or something.