You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by no...@cecosstream.com on 2006/04/01 00:09:48 UTC
[users@httpd] Can apache and ssh share port 80?
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Emmanuel E <em...@gmx.net>.
well if they have a firewall that inspects traffic, tunneling ssh through port 443 wont be met with much joy...
----- Original Message -----
From: Victor Trac
To: users@httpd.apache.org
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 <dr...@maine.edu> 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@cecosstream.com 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
--
---------------------------------+--------------------------------------
Drew Northup | Technical Support Specialist
University of Maine System | Drew.Northup@Maine.edu
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
--
http://www.victortrac.com
Re: [users@httpd] Question Regarding Apache 1.3.33 Installation
Posted by Michael Hosrom <Mi...@Sun.COM>.
Joshua Slive wrote On 04/03/06 13:01,:
> On 4/3/06, Michael Hosrom <Mi...@sun.com> wrote:
>
>>Hi All,
>>
>>My question is in regard to Apache 1.3.33 installation.
>>My system had version 1.3.27 and wanted to install 1.3.33.
>>I stopped and removed 1.3.27, and during the 1.3.33
>>installation, I got the following messages:
>>
>>"Installation was interrupted before Apache http server
>>1.3.33 could be completely installed"
>>
>>Can someone tell me what would cause such interruption?
>>What *other* task(s) must be removed (or made inactive) in
>>order for the installation to be successful?
>
>
> Hmmm... Are we talking about a windows installer here?
Yes. One other point I would like to make is when I removed
the network cable and tried to install 1.3.33 again, it worked.
So, I'm basically interested in the task(s) that would normally
be dependent on getting 1.3.33 (or other versions..) installed.
Thanks,
Mike.
>
> Have you read:
> http://apache.mirrored.ca/httpd/binaries/win32/TROUBLESHOOTING.html
>
> Joshua.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Question Regarding Apache 1.3.33 Installation
Posted by Joshua Slive <jo...@slive.ca>.
On 4/3/06, Michael Hosrom <Mi...@sun.com> wrote:
> Hi All,
>
> My question is in regard to Apache 1.3.33 installation.
> My system had version 1.3.27 and wanted to install 1.3.33.
> I stopped and removed 1.3.27, and during the 1.3.33
> installation, I got the following messages:
>
> "Installation was interrupted before Apache http server
> 1.3.33 could be completely installed"
>
> Can someone tell me what would cause such interruption?
> What *other* task(s) must be removed (or made inactive) in
> order for the installation to be successful?
Hmmm... Are we talking about a windows installer here?
Have you read:
http://apache.mirrored.ca/httpd/binaries/win32/TROUBLESHOOTING.html
Joshua.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Question Regarding Apache 1.3.33 Installation
Posted by Kishore Jalleda <kj...@gmail.com>.
I Would do this....
1) download apache_1.3.33 into some directory ( could be same as the one
holding apache_1.3.27)
3) stop te current apache server running)
4) just build apache_1.3.33 again , with the right directives ( if this
install is the same as 1.3.27 then just copy config.status file from the old
apache_1.3.27 dir and put it in the new apache directory) and then just run
./config.status
make
make install
now start apache and you will see that you have the new version running ....
Kishore Jalleda
http://kjalleda.googlepages.com
On 4/3/06, Michael Hosrom <Mi...@sun.com> wrote:
>
> Hi All,
>
> My question is in regard to Apache 1.3.33 installation.
> My system had version 1.3.27 and wanted to install 1.3.33.
> I stopped and removed 1.3.27, and during the 1.3.33
> installation, I got the following messages:
>
> "Installation was interrupted before Apache http server
> 1.3.33 could be completely installed"
>
> Can someone tell me what would cause such interruption?
> What *other* task(s) must be removed (or made inactive) in
> order for the installation to be successful?
>
> Thanks in advance..
>
> Mike.
>
>
> ---------------------------------------------------------------------
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
[users@httpd] Question Regarding Apache 1.3.33 Installation
Posted by Michael Hosrom <Mi...@Sun.COM>.
Hi All,
My question is in regard to Apache 1.3.33 installation.
My system had version 1.3.27 and wanted to install 1.3.33.
I stopped and removed 1.3.27, and during the 1.3.33
installation, I got the following messages:
"Installation was interrupted before Apache http server
1.3.33 could be completely installed"
Can someone tell me what would cause such interruption?
What *other* task(s) must be removed (or made inactive) in
order for the installation to be successful?
Thanks in advance..
Mike.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by no...@alumni.caltech.edu.
Thanks for all the ideas everyone! I don't think any of them will
quite work for me (I need to have apache on port 443 as well to handle
some https stuff; the DAV is a good idea though I want to be able to
do more than just change files; and the people who run the firewall
are not my clients, but the underlings of the underlings of the bosses
of the bosses of my client, and more interested in their policies than
in my getting work done.) But maybe I can cobble something together
from all your creative ideas.
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Victor Trac <vi...@gmail.com>.
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 <dr...@maine.edu> 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@cecosstream.com 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@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> >
> --
> ---------------------------------+--------------------------------------
> Drew Northup | Technical Support Specialist
> University of Maine System | Drew.Northup@Maine.edu
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
--
http://www.victortrac.com
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Drew Northup <dr...@maine.edu>.
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@cecosstream.com 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
--
---------------------------------+--------------------------------------
Drew Northup | Technical Support Specialist
University of Maine System | Drew.Northup@Maine.edu
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Victor Trac <vi...@gmail.com>.
You can get around this by making SSH listen to 443, as the military
firewall will allow 443 (https) outbound. Another option is to set up
another box to listen to 80 as a proxy to the http server. However, having
ssh listen to both 22 and 443 would be the easiest solution.
Cheers.
On 4/1/06, Jon Snow <js...@gatesec.net> wrote:
>
>
> Bob,
>
> The real question you should be asking is why you would even contemplate
> tunnelling through the paranoid firewall of a military base?
>
> How about buying a dial up link and use their phone, or get them to
> provide a
> stand alone internet connected workstation, then show them the site and
> make
> modifications through that? If they want you to make real time
> modifications
> while you are there they need to provide you with the resources.
>
> Regards,
> Jon
>
>
>
> On Saturday 01 April 2006 08:09, nolty@cecosstream.com 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@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
>
> ---------------------------------------------------------------------
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
--
http://www.victortrac.com
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Jon Snow <js...@gatesec.net>.
Bob,
The real question you should be asking is why you would even contemplate
tunnelling through the paranoid firewall of a military base?
How about buying a dial up link and use their phone, or get them to provide a
stand alone internet connected workstation, then show them the site and make
modifications through that? If they want you to make real time modifications
while you are there they need to provide you with the resources.
Regards,
Jon
On Saturday 01 April 2006 08:09, nolty@cecosstream.com 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Emmanuel E <em...@gmx.net>.
try running ssh on port 443 and use putty to log in.
or
u could run apache+ssl+mod_proxy on port 443 and define an AllowCONNECT to
port 22. u will need to patch mod_proxy for this to work (and some other
stuff too!).
----- Original Message -----
From: <no...@cecosstream.com>
To: <us...@httpd.apache.org>
Sent: Saturday, April 01, 2006 3:39 AM
Subject: [users@httpd] Can apache and ssh share port 80?
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Oscar Haeger <Os...@nbit.sigma.se>.
How about one of the many web-ssh clients out there? Could you perhaps
setup one of those and use that instead?
http://www.google.com/search?hl=en&q=web+ssh&btnG=Google-search&meta=
It's not an ideal solution but it might be what you're looking for.
Oscar
Quoting Emmanuel E <em...@gmx.net>:
> I have a feeling that you should run ssh on port 443 even if you get
> a different IP address, unless its a 'differently' configured
> firewall...
> ----- Original Message ----- From: "Scott Gifford"
> <sg...@suspectclass.com>
> To: <us...@httpd.apache.org>
> Sent: Saturday, April 01, 2006 10:32 AM
> Subject: Re: [users@httpd] Can apache and ssh share port 80?
>
>
>> The easiest way to do this is set up another IP address on the
>> machine, and have ssh listen on port 80 of that address only.
>>
>> ---Scott.
>>
>> ---------------------------------------------------------------------
>> 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@httpd.apache.org
>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>
>
> ---------------------------------------------------------------------
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Emmanuel E <em...@gmx.net>.
I have a feeling that you should run ssh on port 443 even if you get a
different IP address, unless its a 'differently' configured firewall...
----- Original Message -----
From: "Scott Gifford" <sg...@suspectclass.com>
To: <us...@httpd.apache.org>
Sent: Saturday, April 01, 2006 10:32 AM
Subject: Re: [users@httpd] Can apache and ssh share port 80?
> The easiest way to do this is set up another IP address on the
> machine, and have ssh listen on port 80 of that address only.
>
> ---Scott.
>
> ---------------------------------------------------------------------
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by Scott Gifford <sg...@suspectclass.com>.
nolty@cecosstream.com writes:
[...]
> 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.
The easiest way to do this is set up another IP address on the
machine, and have ssh listen on port 80 of that address only.
---Scott.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Can apache and ssh share port 80?
Posted by David Wolever <wo...@gmail.com>.
Hey,
I, personally, run Apache on 80, SSH on 443... Works well and keeps
worms off my back. Your problem DOES remind me of something I
stumbled across a little while ago. Here it is:
http://dag.wieers.com/howto/ssh-http-tunneling/
Tunneling SSH over HTTP
"This document explains how to set up an Apache server and SSH client
to allow tunneling SSH over HTTP(S). This can be useful on restricted
networks that either firewall everything except HTTP traffic
(tcp/80,tcp/443) or require users to use a local (HTTP) proxy."
May not be perfect though... as it requires some tweaking and proxies
and stuff. May help though.
David
On 3/31/06, nolty@cecosstream.com <no...@cecosstream.com> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org