>Number: 1924
>Category: suexec
>Synopsis: VirtualHosts don't work with suexec, why not simply...
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: change-request
>Submitter-Id: apache
>Arrival-Date: Sun Mar 8 16:10:00 PST 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3b5
>Environment:
N/A
>Description:
suexec won't work with VirtualHost's located not in the documentroot,
as already pointed out, you can work around it with changing the path
to a location in the document root.
but wouldn't it be wiser to simply instead of defining one document root,
just taking the environment-variable DOCUMENT_ROOT instead of the #define
DOC_ROOT.
are there any risks ? doesn't apache set these environments safely for every
VirtualHost ? Please send comments to me !!!
>How-To-Repeat:
simply add a VirtualHost with a DocumentRoot set to his home-directory
(e.g. /home/user) suexec won't find the cmd as it is not located in the
main document-root (e.g. /usr/local/apache/htdocs)
>Fix:
instead of using DOC_ROOT from suexec.h, comment the #defines and replace
the DOC_ROOT by getenv("DOCUMENT_ROOT") twice in suexec.c !
Are there any risks involved %3
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
