View previous topic :: View next topic |
Author |
Message |
bugg_tb Apprentice
Joined: 19 Nov 2004 Posts: 282 Location: Leeds, UK
|
Posted: Wed Sep 17, 2008 8:53 am Post subject: SSH & Corporate firewall issues |
|
|
Hi Guys,
For years I ran my ssh server at home on port 80 cause it allowed me to access my box from work. I installed zimbra on the box and would like to run that on its default ports and so I was reading up on ssh over https but I'm not sure if either a) I don't understand it or b) I'm just doing something stupid.
I've tried both proxytunnel and corkscrew with no success, what I am trying to do it run ssh from work which will have to go via port 80 hit my server at home and do apache based proxy redirection to the ssh server running on port 22(ie mail.server.com would redirect to zimbra on port 81 and ssh.server.com would do the ssh stuff) then return the tunnel via port 80, is that possible or have I got to revert to the old way?
Cheers
Tom _________________ Remember, even at a Mensa convention someone is the dumbest person in the room! |
|
Back to top |
|
|
alex.blackbit Advocate
Joined: 26 Jul 2005 Posts: 2397
|
Posted: Wed Sep 17, 2008 11:10 am Post subject: |
|
|
what is ssh over https?
ssh is a layer 7 network protocol, as is https. you do not have one "over" the other.
the dns names you refer to do no have anything to do with tcp ports.
if i get the situation right, you want to ssh home but there are limitations of the tcp ports you can use for that.
AND you want to run a webserver at home on the standard port for zimbra.
there are definitely more ports open you can use, at least 443 for https.
since you seem to be using a unix-like os at work, i'd say, use nmap or write a script to test which ports are open and use one of these. |
|
Back to top |
|
|
bugg_tb Apprentice
Joined: 19 Nov 2004 Posts: 282 Location: Leeds, UK
|
Posted: Wed Sep 17, 2008 12:10 pm Post subject: |
|
|
http://dag.wieers.com/howto/ssh-http-tunneling/
I should probably have put the word tunneling in there as well but even in this example they still run ssh on 443 I was hoping to eliminate the need to run it on a non standard port _________________ Remember, even at a Mensa convention someone is the dumbest person in the room! |
|
Back to top |
|
|
Chris W l33t
Joined: 25 Jun 2002 Posts: 972 Location: Brisbane, Australia
|
Posted: Wed Sep 17, 2008 12:28 pm Post subject: |
|
|
I do something similar. When a new connection comes from the boss' IP address range to port 443 it is redirected to port 22, otherwise it goes through unaffected. PuTTY (ssh client) can then use CONNECT at work's proxy to get out. _________________ Cheers,
Chris W
"Common sense: The collection of prejudices acquired by age 18." -- Einstein |
|
Back to top |
|
|
bugg_tb Apprentice
Joined: 19 Nov 2004 Posts: 282 Location: Leeds, UK
|
Posted: Thu Sep 18, 2008 9:58 am Post subject: |
|
|
Chris W wrote: | I do something similar. When a new connection comes from the boss' IP address range to port 443 it is redirected to port 22, otherwise it goes through unaffected. PuTTY (ssh client) can then use CONNECT at work's proxy to get out. |
Fancy enlightening me a little more with that cause I still haven't quite worked it out _________________ Remember, even at a Mensa convention someone is the dumbest person in the room! |
|
Back to top |
|
|
|