|
well if they have a firewall that
inspects traffic, tunneling ssh through port 443 wont be met with much
joy...
----- Original Message -----
Sent: Sunday, April 02, 2006 8:49
PM
Subject: Re: [users@httpd] Can apache and
ssh share port 80?
I'm not suggesting that anyone should screw with the military's
local firewall. .Mil networks generally allow 80/tcp and 443/tcp
outbound connections, and so making a remote SSH server listen on 443 is just
a way to connect to it while still passing local firewall rules. As far
as the local network is concerned, you're making https connections, and https
is certainly allowed.
On 4/2/06, Drew
Northup <drew.northup@xxxxxxxxx>
wrote:
Uhh...,
don't screw with their firewall--read federal offence.
Either get them to
grant you what you NEED (and no more than
that--unless you really want to
be in deep kimche), or get a different
job.
In any case, have you
thought about using WebDAV over https? Apache
supports this just
fine--and you can even set it up to edit scripts and
includes if you pay
attention. Once you have WebDAV over https running
you can use
damn near whatever you want wherever you want to edit the
content.
On Fri, 2006-03-31 at 14:09 -0800, nolty@xxxxxxxxxxxxxxx wrote:
>
Hi all --
>
> I have a linux box running several websites using
apache. Elsewhere,
> I have a client on a military
base. When I am at the client's site
> using their network,
their paranoid firewall drops just about
> everything in the world
except port 80. This means I can show them
> their website
when I am there, but I can't log on and make changes to
> the
website. Obviously, this makes development very
cumbersome,
> especially since they are 60 miles from my
office.
>
> I would be interested in any ideas about how I could
use port 80 to
> log on to the machine. Currently, I only
allow logins via ssh on port
> 22.
>
> Ideally, I wish
there were some kind of apache directives I could use
> so that httpd
would continue to monitor port 80, and if it gets a
> connection that
does not look like http or https, it would forward the
> bits to port
22. But I doubt that is possible.
>
> Alternatively,
I wondered if I could write a simple Perl program that
> would monitor
port 80; if it got a connection that looked like http or
> https it
would forward it to apache (perhaps on port 81) and otherwise
> it
would forward it to ssh (perhaps on port 22).
>
> Any
ideas?
>
> Thanks,
> Bob
>
>
---------------------------------------------------------------------
>
The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html>
for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
>
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
--
---------------------------------+--------------------------------------
Drew
Northup
| Technical
Support Specialist
University of Maine
System
|
Drew.Northup@xxxxxxxxx
Computing
Center
| phone:
(207)581-3513
Orono, ME
04469 | fax:
(207)581-3531
---------------------------------------------------------------------
The
official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html
> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For
additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--
http://www.victortrac.com
|
