Date: 12 Jan 2000 12:08:15 -0000
Message-ID: <20000112120815.80197.qmail@locus.apache.org>
To: apache-bugdb@apache.org, coar@apache.org, sineswiper@resonatorsoft.com
From: coar@apache.org
Subject: Re: suexec/4435: suEXEC only works on CGIs/SSIs (not very useful for
 permission locking)
Sender: apache-bugdb-owner@apache.org
Precedence: bulk

[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: suEXEC only works on CGIs/SSIs (not very useful for permission locking)

State-Changed-From-To: open-closed
State-Changed-By: coar
State-Changed-When: Wed Jan 12 04:08:14 PST 2000
State-Changed-Why:

Noteh the 'exec' part of suexec's name.  It functions
with Apache by changing the UID/GID of a process to handle
a script, after which the process dies.  That would not
be terribly efficient if done for every single request,
and is contrary to suexec's intended purpose in any event.
I'm afraid that suexec isn't the solution for your problem;
you're going to have to solve it using some OS-level choice
of permissions.  But thanks for asking and for using Apache!