Mailing List Archive

I was playing around with this a couple days ago... You have to do some
tweaking or src/support/suexec.h, then run a make in the of the suexec, and
put it where you told the header file it would be.


-----Original Message-----
From: Geoffrey Young [mailto:gyoung@laserlink.net]
Sent: Tuesday, February 29, 2000 10:43 AM
To: 'modperl@apache.org'
Subject: [Apache config] suEXEC compiled in by default?


hi all...

it seems that suEXEC made it's way into my latest mod_perl httpd (1.3.12),
but at least according to http://www.apache.org/docs/suexec.html suEXEC
should _not_ compiled in by default, and I don't think I did anything to
explicitly add it...

anyway, I'm thinking that maybe suEXEC should not be compiled in mod_perl by
default either?




I'm not familiar at all with using suEXEC, but I did notice the following
from httpd -l today:

suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec

now, I saw that 1.3.12 added a new feature so suexec warnings would show up
in httpd -l, so this may have been the case for a while...

my mod_perl installation just used EVERYTHING=1 (no APACI -
apache_1.3.12/src/Configuration instead)

I tried poking around the Makefile.PL for both Apache and mod_perl to see
where it gets the directive, but couldn't find it...

if anyone else has any interest (or maybe understands what I'm trying to say
:)

--Geoff

ok, so does that mean that suEXEC is not enabled now? in re point 4 of the
apache docs, I'm clearly not really in a position to evaluate the security
risks of suEXEC right now, since I don't even know enough to know if it's
enabled in my installation

:)

--Geoff

> -----Original Message-----
> From: Karyn Ulriksen [mailto:kulriksen@publichost.com]
> Sent: Tuesday, February 29, 2000 1:50 PM
> To: 'Geoffrey Young'
> Cc: 'modperl@apache.org'
> Subject: RE: [Apache config] suEXEC compiled in by default?
>
>
> I was playing around with this a couple days ago... You have
> to do some
> tweaking or src/support/suexec.h, then run a make in the of
> the suexec, and
> put it where you told the header file it would be.
>
>
> -----Original Message-----
> From: Geoffrey Young [mailto:gyoung@laserlink.net]
> Sent: Tuesday, February 29, 2000 10:43 AM
> To: 'modperl@apache.org'
> Subject: [Apache config] suEXEC compiled in by default?
>
>
> hi all...
>
> it seems that suEXEC made it's way into my latest mod_perl
> httpd (1.3.12),
> but at least according to
> http://www.apache.org/docs/suexec.html suEXEC
> should _not_ compiled in by default, and I don't think I did
> anything to
> explicitly add it...
>
> anyway, I'm thinking that maybe suEXEC should not be compiled
> in mod_perl by
> default either?
>
>
>
>
> I'm not familiar at all with using suEXEC, but I did notice
> the following
> from httpd -l today:
>
> suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec
>
> now, I saw that 1.3.12 added a new feature so suexec warnings
> would show up
> in httpd -l, so this may have been the case for a while...
>
> my mod_perl installation just used EVERYTHING=1 (no APACI -
> apache_1.3.12/src/Configuration instead)
>
> I tried poking around the Makefile.PL for both Apache and
> mod_perl to see
> where it gets the directive, but couldn't find it...
>
> if anyone else has any interest (or maybe understands what
> I'm trying to say
> :)
>
> --Geoff
>

No. It's not enabled unless you setup the suexec manually. When you run
the "httpd -l", it will confirm whether suexec is disabled or not.

-----Original Message-----
From: Geoffrey Young [mailto:gyoung@laserlink.net]
Sent: Tuesday, February 29, 2000 10:56 AM
To: 'Karyn Ulriksen'
Cc: 'modperl@apache.org'
Subject: RE: [Apache config] suEXEC compiled in by default?


ok, so does that mean that suEXEC is not enabled now? in re point 4 of the
apache docs, I'm clearly not really in a position to evaluate the security
risks of suEXEC right now, since I don't even know enough to know if it's
enabled in my installation

:)

--Geoff

> -----Original Message-----
> From: Karyn Ulriksen [mailto:kulriksen@publichost.com]
> Sent: Tuesday, February 29, 2000 1:50 PM
> To: 'Geoffrey Young'
> Cc: 'modperl@apache.org'
> Subject: RE: [Apache config] suEXEC compiled in by default?
>
>
> I was playing around with this a couple days ago... You have
> to do some
> tweaking or src/support/suexec.h, then run a make in the of
> the suexec, and
> put it where you told the header file it would be.
>
>
> -----Original Message-----
> From: Geoffrey Young [mailto:gyoung@laserlink.net]
> Sent: Tuesday, February 29, 2000 10:43 AM
> To: 'modperl@apache.org'
> Subject: [Apache config] suEXEC compiled in by default?
>
>
> hi all...
>
> it seems that suEXEC made it's way into my latest mod_perl
> httpd (1.3.12),
> but at least according to
> http://www.apache.org/docs/suexec.html suEXEC
> should _not_ compiled in by default, and I don't think I did
> anything to
> explicitly add it...
>
> anyway, I'm thinking that maybe suEXEC should not be compiled
> in mod_perl by
> default either?
>
>
>
>
> I'm not familiar at all with using suEXEC, but I did notice
> the following
> from httpd -l today:
>
> suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec
>
> now, I saw that 1.3.12 added a new feature so suexec warnings
> would show up
> in httpd -l, so this may have been the case for a while...
>
> my mod_perl installation just used EVERYTHING=1 (no APACI -
> apache_1.3.12/src/Configuration instead)
>
> I tried poking around the Makefile.PL for both Apache and
> mod_perl to see
> where it gets the directive, but couldn't find it...
>
> if anyone else has any interest (or maybe understands what
> I'm trying to say
> :)
>
> --Geoff
>

>
> No. It's not enabled unless you setup the suexec manually.
> When you run
> the "httpd -l", it will confirm whether suexec is disabled or not.

duh... if only I could read :) or maybe some more caffeine...

>
> -----Original Message-----
> From: Geoffrey Young [mailto:gyoung@laserlink.net]
> Sent: Tuesday, February 29, 2000 10:56 AM
> To: 'Karyn Ulriksen'
> Cc: 'modperl@apache.org'
> Subject: RE: [Apache config] suEXEC compiled in by default?
>
>
> ok, so does that mean that suEXEC is not enabled now? in re
> point 4 of the
> apache docs, I'm clearly not really in a position to evaluate
> the security
> risks of suEXEC right now, since I don't even know enough to
> know if it's
> enabled in my installation
>
> :)
>
> --Geoff
>
> > -----Original Message-----
> > From: Karyn Ulriksen [mailto:kulriksen@publichost.com]
> > Sent: Tuesday, February 29, 2000 1:50 PM
> > To: 'Geoffrey Young'
> > Cc: 'modperl@apache.org'
> > Subject: RE: [Apache config] suEXEC compiled in by default?
> >
> >
> > I was playing around with this a couple days ago... You have
> > to do some
> > tweaking or src/support/suexec.h, then run a make in the of
> > the suexec, and
> > put it where you told the header file it would be.
> >
> >
> > -----Original Message-----
> > From: Geoffrey Young [mailto:gyoung@laserlink.net]
> > Sent: Tuesday, February 29, 2000 10:43 AM
> > To: 'modperl@apache.org'
> > Subject: [Apache config] suEXEC compiled in by default?
> >
> >
> > hi all...
> >
> > it seems that suEXEC made it's way into my latest mod_perl
> > httpd (1.3.12),
> > but at least according to
> > http://www.apache.org/docs/suexec.html suEXEC
> > should _not_ compiled in by default, and I don't think I did
> > anything to
> > explicitly add it...
> >
> > anyway, I'm thinking that maybe suEXEC should not be compiled
> > in mod_perl by
> > default either?
> >
> >
> >
> >
> > I'm not familiar at all with using suEXEC, but I did notice
> > the following
> > from httpd -l today:
> >
> > suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec
> >
> > now, I saw that 1.3.12 added a new feature so suexec warnings
> > would show up
> > in httpd -l, so this may have been the case for a while...
> >
> > my mod_perl installation just used EVERYTHING=1 (no APACI -
> > apache_1.3.12/src/Configuration instead)
> >
> > I tried poking around the Makefile.PL for both Apache and
> > mod_perl to see
> > where it gets the directive, but couldn't find it...
> >
> > if anyone else has any interest (or maybe understands what
> > I'm trying to say
> > :)
> >
> > --Geoff
> >
>

sorry - I guess I was originally going on the fact that the apache docs were
saying it was disabled and I was wondering if mod_perl compliation enabled
it by default...

that was on-topic, I would think, but we have strayed at this point...

back to your regularly scheduled list... :)

--Geoff

> -----Original Message-----
> From: Autarch [mailto:autarch@urth.org]
> Sent: Tuesday, February 29, 2000 2:17 PM
> To: Karyn Ulriksen
> Cc: 'Geoffrey Young'; 'modperl@apache.org'
> Subject: RE: [Apache config] suEXEC compiled in by default?
>
>
> On Tue, 29 Feb 2000, Karyn Ulriksen wrote:
>
> > No. It's not enabled unless you setup the suexec manually.
> When you run
> > the "httpd -l", it will confirm whether suexec is disabled or not.
>
> This is pretty off-topic. suEXEC is an Apache feature and
> doesn't have
> much to with mod_perl other than that you cannot get a
> mod_perl registry
> script or handler to run under suEXEC. This would be best moved to an
> Apache specific list.
>
>
> -dave
>
> /*==================
> www.urth.org
> We await the New Sun
> ==================*/
>

On Tue, 29 Feb 2000, Karyn Ulriksen wrote:

> No. It's not enabled unless you setup the suexec manually. When you run
> the "httpd -l", it will confirm whether suexec is disabled or not.

This is pretty off-topic. suEXEC is an Apache feature and doesn't have
much to with mod_perl other than that you cannot get a mod_perl registry
script or handler to run under suEXEC. This would be best moved to an
Apache specific list.


-dave

/*==================
www.urth.org
We await the New Sun
==================*/