I wont get into "what you need to do at job place" - the "contact your sysadmin to ask him about" was already stated. :)
Next, have a look at GNU httptunnel (actually you can install it from cygwin since it's in the package list) and you may even tunnel the ssh connection. The drawback - you need it both running on the server end and client end so you'll have to ask your shell provider to run it too (which I doubt they'll do) or... set up a httptunnel redirector at home computer.
The other possible "tunneling" software might be corckscrew - have a look here and on its homepage.
Final note - it might be easier to reason with your sysadmin, use a live-cd or vmware-install to get around with linux instead of wasting energy into 'getting around' - an aware sysadmin will get you. :) So, if you want to do the shell IRC-ing, do it from home and not at work. :)
June 1st, 2006, 05:49 PM
Originally posted here by RoadClosed TCP Wrapper and SSH Port Forwarding for 1000 Alex.
What is setting up your own box on your home network with its own ssh server running on a commonly allowed port?
June 1st, 2006, 06:56 PM
da da da da da daaa (poor attempt at Jeopardy music)
June 1st, 2006, 07:37 PM
Originally posted here by RoadClosed da da da da da daaa (poor attempt at Jeopardy music)
I was thinking more along the lines of Twilight Zone..... :p
June 1st, 2006, 09:26 PM
That's a good idea.... I probably would be able to set up an ssh server at home on port 80 or something else just as common. One guy stated earlier that it might filter applications as well.
I guess we'll just have to see what happens once I set up a home machine.
Thanks for the help.
June 1st, 2006, 09:44 PM
If there is good security gear ala IPS/IDS and such in place, the port will make no difference as the protocol filter will see the SSH negotiation. You can guess what happens next when the sec admin gets the alert. My advice would be to wear some body armor cause sec admins prefer aluminum bats.
June 2nd, 2006, 02:36 AM
Originally posted here by thehorse13 If there is good security gear ala IPS/IDS and such in place, the port will make no difference as the protocol filter will see the SSH negotiation. You can guess what happens next when the sec admin gets the alert. My advice would be to wear some body armor cause sec admins prefer aluminum bats.
Hense, my warning. ;) He would get that by me on my network. ;)
if you can install software put vmware player on and set it up to run a live cd. if you dont have the rights to install you shouldn't even be asking these questions unless your goal is to be a carpenter but having Auditor running on your box can be allot more fun that a shell account plus you can still do your work on windows
June 2nd, 2006, 05:02 AM
Re: I thought...
Originally posted here by hunterhunter I figured that port 22 was blocked. That was obvious.
I was just thinking that I could set putty up to make the request over port 80. Thence my ssh tunnel would be entering through port 80, unobstructed.... I guess that I was wrong. The server that I'm trying to connect to must also be set to communicate through port 80 for ssh as well then.
Atleast, I think...
There's no way that the admins here will unblock ssh, simply, because we don't use it.
This basically means that I can't use UNIX/Linux at work whatsoever then :(....
I really need shell access to practice, I instaled Cygwin... but it's not the same...
I might just have to use vmware player and run a live distro while in Winblows but an encrypted tunnel would be much nicer.
If you guys have anymore ideas then PLEASE don't hesitate so that I can try them....
Thanks for the assists.
hunterhunter. I know that your security admin wouldn't let you go with the 22 port open. So, why not you try to tunnel by visit this website? You will learn much about it.
If you don't have unix or linux box, try this :