You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2004/03/23 04:52:15 UTC
cvs commit: httpd-2.0/docs/manual suexec.html.en suexec.xml
slive 2004/03/22 19:52:15
Modified: docs/manual suexec.html.en suexec.xml
Log:
Mention that mod_userdir is required for suexec to work
in user directories.
PR: 25477
Revision Changes Path
1.51 +13 -10 httpd-2.0/docs/manual/suexec.html.en
Index: suexec.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/suexec.html.en,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -d -b -u -r1.50 -r1.51
--- suexec.html.en 21 Feb 2004 00:31:29 -0000 1.50
+++ suexec.html.en 23 Mar 2004 03:52:15 -0000 1.51
@@ -528,6 +528,10 @@
<div class="section">
<h2><a name="usage" id="usage">Using suEXEC</a></h2>
+ <p>Requests for CGI programs will call the suEXEC wrapper only if
+ they are for a virtual host containing a <code class="directive"><a href="./mod/mod_suexec.html#suexecusergroup">SuexecUserGroup</a></code> directive or if
+ they are processed by <code class="module"><a href="./mod/mod_userdir.html">mod_userdir</a></code>.</p>
+
<p><strong>Virtual Hosts:</strong><br /> One way to use the suEXEC
wrapper is through the <code class="directive"><a href="./mod/mod_suexec.html#suexecusergroup">SuexecUserGroup</a></code> directive in
<code class="directive"><a href="./mod/core.html#virtualhost">VirtualHost</a></code> definitions. By
@@ -537,16 +541,15 @@
directive is not specified for a <code class="directive"><a href="./mod/core.html#virtualhost"><VirtualHost></a></code> then the main server userid
is assumed.</p>
- <p><strong>User directories:</strong><br />
- The suEXEC wrapper can also be used to execute CGI programs as
- the user to which the request is being directed. This is
- accomplished by using the "<strong><code>~</code></strong>"
- character prefixing the user ID for whom execution is desired.
- The only requirement needed for this feature to work is for CGI
- execution to be enabled for the user and that the script must
- meet the scrutiny of the <a href="#model">security checks</a>
- above.</p>
-</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+ <p><strong>User directories:</strong><br /> Requests that are
+ processed by <code class="module"><a href="./mod/mod_userdir.html">mod_userdir</a></code> will call the suEXEC
+ wrapper to execute CGI programs under the userid of the requested
+ user directory. The only requirement needed for this feature to
+ work is for CGI execution to be enabled for the user and that the
+ script must meet the scrutiny of the <a href="#model">security
+ checks</a> above. See also the
+ <code>--with-suexec-userdir</code> <a href="#install">compile
+ time option</a>.</p> </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
<h2><a name="debug" id="debug">Debugging suEXEC</a></h2>
1.13 +14 -10 httpd-2.0/docs/manual/suexec.xml
Index: suexec.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/suexec.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -b -u -r1.12 -r1.13
--- suexec.xml 9 Feb 2004 20:20:06 -0000 1.12
+++ suexec.xml 23 Mar 2004 03:52:15 -0000 1.13
@@ -517,6 +517,11 @@
<section id="usage"><title>Using suEXEC</title>
+ <p>Requests for CGI programs will call the suEXEC wrapper only if
+ they are for a virtual host containing a <directive
+ module="mod_suexec">SuexecUserGroup</directive> directive or if
+ they are processed by <module>mod_userdir</module>.</p>
+
<p><strong>Virtual Hosts:</strong><br /> One way to use the suEXEC
wrapper is through the <directive
module="mod_suexec">SuexecUserGroup</directive> directive in
@@ -529,16 +534,15 @@
type="section">VirtualHost</directive> then the main server userid
is assumed.</p>
- <p><strong>User directories:</strong><br />
- The suEXEC wrapper can also be used to execute CGI programs as
- the user to which the request is being directed. This is
- accomplished by using the "<strong><code>~</code></strong>"
- character prefixing the user ID for whom execution is desired.
- The only requirement needed for this feature to work is for CGI
- execution to be enabled for the user and that the script must
- meet the scrutiny of the <a href="#model">security checks</a>
- above.</p>
-</section>
+ <p><strong>User directories:</strong><br /> Requests that are
+ processed by <module>mod_userdir</module> will call the suEXEC
+ wrapper to execute CGI programs under the userid of the requested
+ user directory. The only requirement needed for this feature to
+ work is for CGI execution to be enabled for the user and that the
+ script must meet the scrutiny of the <a href="#model">security
+ checks</a> above. See also the
+ <code>--with-suexec-userdir</code> <a href="#install">compile
+ time option</a>.</p> </section>
<section id="debug"><title>Debugging suEXEC</title>