ble it globally, just rename
/usr/lib/apache/suexec to something else, but be aware that you will
have to repeat this every time you upgrade your apache package.
--
The freedoms that we enjoy presently are the most important victories of the
White Hats over the past several millennia, and it is v
Hi All,
Is there anyway that I can disable suexec for a certain user or replace
it? I would rather try to avoid a recompile if poss
Rgds
Rus
--
http://www.65535.net | MSN: [EMAIL PROTECTED] | e: [EMAIL PROTECTED]
"More bits for your bite"
Lifetime FreeBSD + Linux Hostin
I have recompiled apache for suexec to use /home as DocumentRoot.
I am trying to get suexec to work and have success when I use one
virtual host with the following configuration:
---
In /opt/apache/conf/httpd.conf I have inter alia:
-
NameVirtualHost *
...
Include httpd
hi there,
i set up virtual hosts with apache an for each a different user.
this way, everything works fine... :)
but as i have all the mail users and domains and the ftp users
in a mysql database, i'd like to have the vhost-users in a db,
too. i tried to find some documentation about suexec and
On 16 Oct 2002, Justin Ryan wrote:
> [2002-10-14 01:29:28]: error: command not in docroot
> (/site.com/cgi-bin/index.py)
>
> The DocumentRoot in this case would be /site.com/www/, and the
> ScriptAlias /site.com/cgi-bin/.
I believe that Debian's provided suexec should be built with docroot as
"
> Not sure, but I think you should arrange all vhosts under the docroot of
> the main server.
>
> Extract from suexec docs:
>
> For security and efficiency reasons, all suexec requests must remain
> within either a top-level document root for virtual host requests, or
> one top-level personal do
Heya all..
I'm having trouble with Apache/SUEXEC on my woody system.. I have some
vhosts that need to run their own cgi scripts. This all works fine,
until I add User/Group directives into the VirtualHost configuration.
I have a ScriptAlias directive and Options +ExecCGI on the direct
eroot debian/rules binary
> Anyhow, so anyone know if there's a way to make apache debs run
> su-exec? thanks.
The debs already have suexec, but the suexec-docroot is set to /var/www or
something like that. If that's not what you want, you'll have to
recompile. Just make
On Mon, Sep 09, 2002 at 03:36:33PM -0700, Forrest English wrote:
| Is there a way to run apache in suexec mode without compiling by hand?
Yes.
| Anyhow, so anyone know if there's a way to make apache debs run
| su-exec? thanks.
They come that way. All you have to do is play by the rules for
s
Is there a way to run apache in suexec mode without compiling by hand? I
havn't used the debian packages of apache in awhile because i started
compiling from source awhile ago to keep scripts running as the user who
owns the script. But I'm tired of compiling, and if i can use the .deb's,
that'
I have a user who would like to execute his own perl-scripts on my server, and
i've read the apache.org docs about suexec. But i canøt really get it to work.
Has anyone got a working configuretion file that i could have a look at ?
Thanks in advance
--
Best Regards / Venlig Hilsen
Rasmu
changes in suid.conf,
> > then suidmanager will upon every restart clear the suid bit of the suexec
> > binary, preventing apache to run.
>
> I just installed suidmanager (sounds like something that is good to
> have) and got an /etc/suid.conf which had nothing in it at all.
r the suid bit of the suexec
> binary, preventing apache to run.
I just installed suidmanager (sounds like something that is good to
have) and got an /etc/suid.conf which had nothing in it at all. Will
this cause me problems? What line should I add for apache suexec?
Thanks again,
Stuart.
>
> > put 4755 in /etc/suid.conf in the line of /usr/lib/apache/suexec instead
> > of 0755, and change apache-common to user.
>
> I don't have an /etc/suid.conf. Is this a package that I should have
> installed, but don't? (I broke my installation early o
ny message about it being found in my
> > error.log (the apache documentation says I should). When I try to enable
> > it by setting a User and Group in a virtualhost directive, I get:
>
> chmod 4755 /usr/lib/apache/suexec
Doing this seemed to work. Thanks!
> put 4755 in /etc/suid.co
e apache documentation says I should). When I try to enable
> it by setting a User and Group in a virtualhost directive, I get:
chmod 4755 /usr/lib/apache/suexec
put 4755 in /etc/suid.conf in the line of /usr/lib/apache/suexec instead
of 0755, and change apache-common to user.
Robert Varga
setting a User and Group in a virtualhost directive, I get:
# /etc/init.d/apache start
Starting web server: apache... failed.
# apachectl configtest
ERROR: User directive in requires SUEXEC wrapper.
Oh, and ls -l /usr/lib/apache/suexec gives
-rwxr-xr-x1 root root 9916 Oct 30 23
-BEGIN PGP SIGNED MESSAGE-
Package: apache
Version: 1.3.6-15.2
Changing the SuExec docroot from /var/www/htdocs to /var/www will enable
SuExec for people without or with few virtual hosts residing below
/var/www.
However, on "bigger" systems with lots of virtual hosts, one might want to
On Sat, 13 Jun 1998, Paul Miller wrote:
> On Sat, 13 Jun 1998, Gergely Madarasz wrote:
> > If you set suexec up in /etc/suid.conf then it wont mess with it afaik.
> > Thats what suidmanager is for.
> no.. when updating apache, the installation script modifies
> /etc/suid.conf too... I think I'll
On Sat, 13 Jun 1998, Gergely Madarasz wrote:
> On Sat, 13 Jun 1998, Paul Miller wrote:
>
> >
> > ... I guess it doesn't make any sense that the package messes up my
> > configuration. Oh well...
>
> If you set suexec up in /etc/suid.conf then it wont mess with it afaik.
> Thats what suidmanage
On Sat, 13 Jun 1998, Paul Miller wrote:
>
> ... I guess it doesn't make any sense that the package messes up my
> configuration. Oh well...
If you set suexec up in /etc/suid.conf then it wont mess with it afaik.
Thats what suidmanager is for.
Greg
--
Madarasz Gergely [EMAIL PROTECTE
t; suexec to 0755 instead of 4711?
> >
> > Every time I upgrade apache, I have to re-edit the suexec.h file,
> > recompile, and change the file mode to 4711 ... it's getting kind of
> > annoying.
>
> setting the right modes in /etc/suid.conf and/or chmod +s
>
etting kind of
> annoying.
setting the right modes in /etc/suid.conf and/or chmod +s
/usr/lib/apache/suexec should be enough. Actually it is enough, I used
this solution and it works. And the default suid is off because i guess
not all sites want it suid... and it is wise to keep the number of
Is there a reason Debian's suidmanager program sets the file mode of
suexec to 0755 instead of 4711?
Every time I upgrade apache, I have to re-edit the suexec.h file,
recompile, and change the file mode to 4711 ... it's getting kind of
annoying.
-Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
Why does the apache maintaince script change the permission of suexec to
755? Apache wants it to be 4711.
-Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
25 matches
Mail list logo
