Re: Access SSH server via HTTP proxy
- From: Darren Dunham <ddunham@xxxxxxxxxxxxxxxx>
- Date: Tue, 24 Oct 2006 00:08:49 GMT
Mark <markbpan@xxxxxxxxxxxxxx> wrote:
On Mon, 23 Oct 2006 14:59:19 -0700, Doug wrote:
Apparently setting up sshd listening on 443 or 8080 would be fine.
I have always set my home ssh server on port 443 for this reason and it
has worked for me. Does anybody know whether this will always work in
all environments? Or are there "deep inspection" corporate firewalls
that can discern the ssh content (the setup at least) and block it (but
still pass normal https)?
I don't know about 'discern the ssh content', but you could use a web
proxy instead of a normal firewall. Such a device could participate in
the HTTPS connection, which the ssh client would not conduct. That
would prevent basic use of the port. You could still tunnel traffic,
but it would have to be done within an HTTPS transport rather than
directly via TCP/443.
The first hit for me on google turned up this page:
http://dag.wieers.com/howto/ssh-http-tunneling/
--
Darren Dunham ddunham@xxxxxxxx
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
.
- References:
- Access SSH server via HTTP proxy
- From: Doug
- Re: Access SSH server via HTTP proxy
- From: Todd H.
- Re: Access SSH server via HTTP proxy
- From: hasenhei
- Re: Access SSH server via HTTP proxy
- From: Doug
- Re: Access SSH server via HTTP proxy
- From: hasenhei
- Re: Access SSH server via HTTP proxy
- From: Doug
- Re: Access SSH server via HTTP proxy
- From: Todd H.
- Re: Access SSH server via HTTP proxy
- From: Doug
- Re: Access SSH server via HTTP proxy
- From: Mark
- Access SSH server via HTTP proxy
- Prev by Date: Re: Access SSH server via HTTP proxy
- Next by Date: Re: Access SSH server via HTTP proxy
- Previous by thread: Re: Access SSH server via HTTP proxy
- Next by thread: Re: Access SSH server via HTTP proxy
- Index(es):
Relevant Pages
|
|