You are viewing a plain text version of this content. The canonical link for it is here.

Posted to apache-bugdb@apache.org by co...@decus.org on 1997/04/24 17:04:56 UTC

Changed information for PR suexec/319

Synopsis: suexec and server side includes

State-Changed-From-To: open-feedback
State-Changed-By: coar@decus.org
State-Changed-When: Thu Apr 24 08:04:55 PDT 1997
State-Changed-Why:
The suexec-bounded environment is very restricted, for
obvious reasons.  One of the restrictions is a severely
limited PATH envariable.  The PATH is set to
"/usr/local/bin:/usr/bin:/bin".  However, I should think
that your ls(1) command should be found somewhere in
there.  What does the error log contain regarding the
#exec cmd request?

Re: Changed information for PR suexec/319

Posted by Marc Slemko <ma...@znep.com>.

No, I think this is a real bug.  You can't run something like /bin/ls
through suexec as things stand now.  Fixing it is another issue.

On Thu, 24 Apr 1997 coar@decus.org wrote:

> Synopsis: suexec and server side includes
> 
> State-Changed-From-To: open-feedback
> State-Changed-By: coar@decus.org
> State-Changed-When: Thu Apr 24 08:04:55 PDT 1997
> State-Changed-Why:
> The suexec-bounded environment is very restricted, for
> obvious reasons.  One of the restrictions is a severely
> limited PATH envariable.  The PATH is set to
> "/usr/local/bin:/usr/bin:/bin".  However, I should think
> that your ls(1) command should be found somewhere in
> there.  What does the error log contain regarding the
> #exec cmd request?
>