From b209756b03e38ce4580a03b112c7d91fde432a3d Mon Sep 17 00:00:00 2001 From: Ken Coar Date: Tue, 24 Jun 1997 18:39:39 +0000 Subject: [PATCH] Removal of the Evil TAB Characters. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78364 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/custom-error.html | 4 +- docs/manual/custom-error.html.en | 4 +- docs/manual/misc/fin_wait_2.html | 114 +++++------ docs/manual/misc/index.html | 28 +-- docs/manual/mod/mod_auth_anon.html | 80 ++++---- docs/manual/mod/mod_include.html | 12 +- docs/manual/mod/mod_proxy.html | 4 +- docs/manual/mod/mod_rewrite.html | 8 +- docs/manual/mod/mod_status.html | 2 +- docs/manual/platform/perf.html | 4 +- docs/manual/process-model.html | 6 +- docs/manual/suexec.html | 313 +++++++++++++++-------------- docs/manual/suexec.html.en | 313 +++++++++++++++-------------- 13 files changed, 447 insertions(+), 445 deletions(-) diff --git a/docs/manual/custom-error.html b/docs/manual/custom-error.html index 3f04af058b..3165ec044e 100644 --- a/docs/manual/custom-error.html +++ b/docs/manual/custom-error.html @@ -29,9 +29,9 @@ response, then this response can be replaced with either some friendlier text or by a redirection to another URL (local or external). - +

- +

Old behavior
NCSA httpd 1.3 would return some boring old error/problem message diff --git a/docs/manual/custom-error.html.en b/docs/manual/custom-error.html.en index 3f04af058b..3165ec044e 100644 --- a/docs/manual/custom-error.html.en +++ b/docs/manual/custom-error.html.en @@ -29,9 +29,9 @@ response, then this response can be replaced with either some friendlier text or by a redirection to another URL (local or external). - +

- +

Old behavior
NCSA httpd 1.3 would return some boring old error/problem message diff --git a/docs/manual/misc/fin_wait_2.html b/docs/manual/misc/fin_wait_2.html index 48e10874af..2d9e946d17 100644 --- a/docs/manual/misc/fin_wait_2.html +++ b/docs/manual/misc/fin_wait_2.html @@ -57,13 +57,13 @@ not send back a FIN and ACK to the server. This means that the connection stays in the FIN_WAIT_2 state until one of the following happens:

If you are lucky, this means that the buggy client will fully close the connection and release the resources on your server. However, there @@ -77,16 +77,16 @@ TCP implementation.

The clients on which this problem has been verified to exist:

This does not appear to be a problem on:

@@ -155,56 +155,56 @@ violation of the RFC, but it is widely recognized as being necessary. The following systems are known to have a timeout:

The following systems are known to not have a timeout:

There is a diff --git a/docs/manual/misc/index.html b/docs/manual/misc/index.html index 127b1f2f0d..2b44c66131 100644 --- a/docs/manual/misc/index.html +++ b/docs/manual/misc/index.html @@ -21,92 +21,92 @@

API
Description of Apache's Application Programming Interface.
FAQ
Frequently-Asked Questions concerning the Apache project and server
Reading Client Input in Apache 1.2
Describes differences between Apache 1.1 and 1.2 in how modules read information from the client
Compatibility with NCSA
Notes about Apache's compatibility with the NCSA server
FIN_WAIT_2
A description of the causes of Apache processes going into the FIN_WAIT_2 state, and what you can do about it
"How-To"
Instructions about how to accomplish some commonly-desired server functionality changes
Known Bugs
Just what it says - a list of known bugs in each of the Apache releases
No PGP
Why we took PEM and PGP support out of the base Apache distribution
Performance Notes (BSD 4.4)
Some notes about ways to improve/optimize Apache performance on BSD 4.4 systems
Performance Notes (Digital UNIX)
Extracts of USENET postings describing how to optimize Apache performance on Digital UNIX systems
Performance Notes (General)
Some generic notes about how to improve Apache performance
Security Tips
Some "do"s - and "don't"s - for keeping your Apache web site secure
Virtual Hosts (IP-based)
Excerpts and notes about configuring and using Apache IP-based virtual hosts
Windows Bug with Web Keepalive
A brief description of a known problem with Microsoft Windows and diff --git a/docs/manual/mod/mod_auth_anon.html b/docs/manual/mod/mod_auth_anon.html index c880c34ee1..c1b6933053 100644 --- a/docs/manual/mod/mod_auth_anon.html +++ b/docs/manual/mod/mod_auth_anon.html @@ -61,23 +61,23 @@ allows users to share URLs. Status: Extension
Module: mod_auth_anon

- A list of one or more 'magic' userIDs which are allowed access - without password verification. The userIDs are space separated. - It is possible to use the ' and " quotes to allow a space in - a userID as well as the \ escape character. -

- Please note that the comparison is case-IN-sensitive. -
- I strongly suggest that the magic username 'anonymous' - is always one of the allowed userIDs. -

- Example:
- - Anonymous: anonymous "Not Registered" 'I don\'t know' -

- This would allow the user to enter without password verification - by using the userId's 'anonymous', 'AnonyMous','Not Registered' and - 'I Don't Know'. + A list of one or more 'magic' userIDs which are allowed access + without password verification. The userIDs are space separated. + It is possible to use the ' and " quotes to allow a space in + a userID as well as the \ escape character. +

+ Please note that the comparison is case-IN-sensitive. +
+ I strongly suggest that the magic username 'anonymous' + is always one of the allowed userIDs. +

+ Example:
+ + Anonymous: anonymous "Not Registered" 'I don\'t know' +

+ This would allow the user to enter without password verification + by using the userId's 'anonymous', 'AnonyMous','Not Registered' and + 'I Don't Know'.

Anonymous_Authoritative

 @@ -91,12 +91,12 @@ allows users to share URLs. When set 'on', there is no fall-through to other authorization methods. So if a userID does not match the values specified in the - Anonymous directive, access is denied. -

- Be sure you know what you are doing when you decide to switch - it on. And remember that it is the linking order of the modules - (in the Configuration / Make file) which details the order - in which the Authorization modules are queried. + Anonymous directive, access is denied. +

+ Be sure you know what you are doing when you decide to switch + it on. And remember that it is the linking order of the modules + (in the Configuration / Make file) which details the order + in which the Authorization modules are queried.

Anonymous_LogEmail

 @@ -107,8 +107,8 @@ allows users to share URLs. Status: Extension
Module: mod_auth_anon

- When set 'on', the default, the 'password' entered (which hopefully - contains a sensible email address) is logged in the httpd-log file. + When set 'on', the default, the 'password' entered (which hopefully + contains a sensible email address) is logged in the httpd-log file.

Anonymous_MustGiveEmail

 @@ -120,8 +120,8 @@ allows users to share URLs. Status: Extension
Module: mod_auth_anon

- Specifies whether the user must specify an email - address as the password. This prohibits blank passwords. + Specifies whether the user must specify an email + address as the password. This prohibits blank passwords.

Anonymous_NoUserID

 @@ -132,11 +132,11 @@ allows users to share URLs. Status: Extension
Module: mod_auth_anon

- When set 'on', users can leave - the userID (and perhaps the password field) empty. This - can be very convenient for MS-Explorer users who can - just hit return or click directly on the OK button; which - seems a natural reaction. + When set 'on', users can leave + the userID (and perhaps the password field) empty. This + can be very convenient for MS-Explorer users who can + just hit return or click directly on the OK button; which + seems a natural reaction.

@@ -148,9 +148,9 @@ allows users to share URLs. Status: Extension
Module: mod_auth_anon

- When set 'on' the 'password' entered is - checked for at least one '@' and a '.' to encourage users to enter - valid email addresses (see the above Auth_LogEmail). + When set 'on' the 'password' entered is + checked for at least one '@' and a '.' to encourage users to enter + valid email addresses (see the above Auth_LogEmail).

Example

 @@ -180,10 +180,10 @@ Excerpt of access.conf:
Anonymous anonymous guest www test welcome

-Anonymous_MustGiveEmail on
+Anonymous_MustGiveEmail on
Anonymous_VerifyEmail on
-Anonymous_NoUserId off
-Anonymous_LogEmail on
+Anonymous_NoUserId off
+Anonymous_LogEmail on

AuthName Use 'anonymous' & Email address for guest entry
AuthType basic

@@ -217,8 +217,8 @@ This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996.

Version 0.5
Added 'VerifyEmail' and 'LogEmail' options. Multiple - 'anonymous' tokens allowed. more docs. Added Authoritative - functionality. + 'anonymous' tokens allowed. more docs. Added Authoritative + functionality.
diff --git a/docs/manual/mod/mod_include.html b/docs/manual/mod/mod_include.html index 6f51130998..f1576471e6 100644 --- a/docs/manual/mod/mod_include.html +++ b/docs/manual/mod/mod_include.html @@ -309,15 +309,15 @@ elements are: Unix egrep command.
( test_condition ) -
true if test_condition is true +
true if test_condition is true
! test_condition -
true if test_condition is false +
true if test_condition is false
test_condition1 && test_condition2 -
true if both test_condition1 and - test_condition2 are true +
true if both test_condition1 and + test_condition2 are true
test_condition1 || test_condition2 -
true if either test_condition1 or - test_condition2 is true +
true if either test_condition1 or + test_condition2 is true

"=" and "!=" bind more tightly than "&&" and diff --git a/docs/manual/mod/mod_proxy.html b/docs/manual/mod/mod_proxy.html index e0aef68846..30926d4da6 100644 --- a/docs/manual/mod/mod_proxy.html +++ b/docs/manual/mod/mod_proxy.html @@ -297,7 +297,7 @@ disables caching completely.

  • Using Netscape hostname shortcuts
  • Why doesn't file type xxx download via FTP?
  • Why does Apache start more slowly when using the - proxy module? + proxy module?
  • Can I use the Apache proxy module with my SOCKS proxy? @@ -337,7 +337,7 @@ application/octet-stream bin dms lha lzh exe class tgz taz

    Why does Apache start more slowly when using the - proxy module?

    + proxy module? If you're using the ProxyBlock or NoCache directives, hostnames' IP addresses are looked up and cached during diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html index 03eaa5801f..8d432e4c4e 100644 --- a/docs/manual/mod/mod_rewrite.html +++ b/docs/manual/mod/mod_rewrite.html @@ -988,10 +988,10 @@ comma-separated list of the following flags: which will be expanded. You can use this flag more than once to set more than one variable. The variables can be later dereferenced at a lot of situations, but the usual location will be from within XSSI (via - <!--#echo var="VAR"-->) or CGI (e.g. $ENV{'VAR'}). - But additionally you can also dereference it in a following RewriteCond - pattern via %{ENV:VAR}. Use this to strip but remember - information from URLs. + <!--#echo var="VAR"-->) or CGI (e.g. $ENV{'VAR'}). + But additionally you can also dereference it in a following RewriteCond + pattern via %{ENV:VAR}. Use this to strip but remember + information from URLs.

    diff --git a/docs/manual/mod/mod_status.html b/docs/manual/mod/mod_status.html index f5a55fa397..f671ad7836 100644 --- a/docs/manual/mod/mod_status.html +++ b/docs/manual/mod/mod_status.html @@ -90,7 +90,7 @@ mark@ukweb.com and tell me your configuration. Do this by adding the following to the AUX_CFLAGS line in the "Configuration" file and then recompiling as usual. 

    -	AUX_CFLAGS= (something) -DSTATUS
+        AUX_CFLAGS= (something) -DSTATUS
    diff --git a/docs/manual/platform/perf.html b/docs/manual/platform/perf.html index 450536257a..566cc0f271 100644 --- a/docs/manual/platform/perf.html +++ b/docs/manual/platform/perf.html @@ -61,9 +61,9 @@ Digital UNIX

    diff --git a/docs/manual/process-model.html b/docs/manual/process-model.html index c130decffa..2c37337b70 100644 --- a/docs/manual/process-model.html +++ b/docs/manual/process-model.html @@ -39,9 +39,9 @@ as too confusing. The defaults for each variable are: 
    -MinSpareServers		5
-MaxSpareServers		10
-StartServers		5
+MinSpareServers         5
+MaxSpareServers         10
+StartServers            5
    There is an absolute maximum number of simultaneous children defined diff --git a/docs/manual/suexec.html b/docs/manual/suexec.html index 7806bc8f55..0157cd0c1b 100644 --- a/docs/manual/suexec.html +++ b/docs/manual/suexec.html @@ -17,14 +17,15 @@

      - CONTENTS -
    1. What is suEXEC?
      2. -
    2. Before we begin.
      3. -
    3. suEXEC Security Model.
      4. -
    4. Configuring & Installing suEXEC
      5. -
    5. Enabling & Disabling suEXEC
      6. -
    6. Debugging suEXEC
      7. -
    7. Beware the Jabberwock: Warnings & Examples
      8. + CONTENTS +
    8. What is suEXEC?
      9. +
    9. Before we begin.
      10. +
    10. suEXEC Security Model.
      11. +
    11. Configuring & Installing suEXEC
      12. +
    12. Enabling & Disabling suEXEC
      13. +
    13. Debugging suEXEC
      14. +
    14. Beware the Jabberwock: Warnings & + Examples

    @@ -119,124 +120,124 @@ user and group IDs under which the program is to execute. The wrapper then employs the following process to determine success or failure -- if any one of these conditions fail, the program logs the failure and exits with an error, otherwise it will continue: -
      -
    1. Was the wrapper called with the proper number of arguments? -
      - The wrapper will only execute if it is given the proper number of arguments. - The proper argument format is known to the Apache web server. If the wrapper - is not receiving the proper number of arguments, it is either being hacked, or - there is something wrong with the suEXEC portion of your Apache binary. -
      -
      2. -
    2. Is the user executing this wrapper a valid user of this system? -
      - This is to ensure that the user executing the wrapper is truly a user of the system. -
      -
      3. -
    3. Is this valid user allowed to run the wrapper? -
      - Is this user the user allowed to run this wrapper? Only one user (the Apache - user) is allowed to execute this program. -
      -
      4. -
    4. Does the target program have an unsafe hierarchical reference? -
      - Does the target program contain a leading '/' or have a '..' backreference? These - are not allowed; the target program must reside within the Apache webspace. -
      -
      5. -
    5. Is the target user name valid? -
      - Does the target user exist? -
      -
      6. -
    6. Is the target group name valid? -
      - Does the target group exist? -
      -
      7. -
    7. Is the target user NOT superuser? -
      - Presently, suEXEC does not allow 'root' to execute CGI/SSI programs. -
      -
      8. -
    8. Is the target userid ABOVE the minimum ID number? -
      - The minimum user ID number is specified during configuration. This allows you - to set the lowest possible userid that will be allowed to execute CGI/SSI programs. - This is useful to block out "system" accounts. -
      -
      9. -
    9. Is the target group NOT the superuser group? -
      - Presently, suEXEC does not allow the 'root' group to execute CGI/SSI programs. -
      -
      10. -
    10. Is the target groupid ABOVE the minimum ID number? -
      - The minimum group ID number is specified during configuration. This allows you - to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. - This is useful to block out "system" groups. -
      -
      11. -
    11. Can the wrapper successfully become the target user and group? -
      - Here is where the program becomes the target user and group via setuid and setgid - calls. The group access list is also initialized with all of the groups of which - the user is a member. -
      -
      12. -
    12. Does the directory in which the program resides exist? -
      - If it doesn't exist, it can't very well contain files. -
      -
      13. -
    13. Is the directory within the Apache webspace? -
      - If the request is for a regular portion of the server, is the requested directory - within the server's document root? If the request is for a UserDir, is the requested - directory within the user's document root? -
      -
      14. -
    14. Is the directory NOT writable by anyone else? -
      - We don't want to open up the directory to others; only the owner user may be able - to alter this directories contents. -
      -
      15. -
    15. Does the target program exist? -
      - If it doesn't exists, it can't very well be executed. -
      -
      16. -
    16. Is the target program NOT writable by anyone else? -
      - We don't want to give anyone other than the owner the ability to change the program. -
      -
      17. -
    17. Is the target program NOT setuid or setgid? -
      - We do not want to execute programs that will then change our UID/GID again. -
      -
      18. -
    18. Is the target user/group the same as the program's user/group? -
      - Is the user the owner of the file? -
      -
      19. -
    19. Can we successfully clean the process environment to ensure safe operations? -
      - suEXEC cleans the process' environment by establishing a safe execution PATH (defined - during configuration), as well as only passing through those variables whose names - are listed in the safe environment list (also created during configuration). -
      -
      20. -
    20. Can we successfully become the target program and execute? -
      - Here is where suEXEC ends and the target program begins. -
      -
      21. -
    +
      +
    1. Was the wrapper called with the proper number of arguments? +
      + The wrapper will only execute if it is given the proper number of arguments. + The proper argument format is known to the Apache web server. If the wrapper + is not receiving the proper number of arguments, it is either being hacked, or + there is something wrong with the suEXEC portion of your Apache binary. +
      +
      2. +
    2. Is the user executing this wrapper a valid user of this system? +
      + This is to ensure that the user executing the wrapper is truly a user of the system. +
      +
      3. +
    3. Is this valid user allowed to run the wrapper? +
      + Is this user the user allowed to run this wrapper? Only one user (the Apache + user) is allowed to execute this program. +
      +
      4. +
    4. Does the target program have an unsafe hierarchical reference? +
      + Does the target program contain a leading '/' or have a '..' backreference? These + are not allowed; the target program must reside within the Apache webspace. +
      +
      5. +
    5. Is the target user name valid? +
      + Does the target user exist? +
      +
      6. +
    6. Is the target group name valid? +
      + Does the target group exist? +
      +
      7. +
    7. Is the target user NOT superuser? +
      + Presently, suEXEC does not allow 'root' to execute CGI/SSI programs. +
      +
      8. +
    8. Is the target userid ABOVE the minimum ID number? +
      + The minimum user ID number is specified during configuration. This allows you + to set the lowest possible userid that will be allowed to execute CGI/SSI programs. + This is useful to block out "system" accounts. +
      +
      9. +
    9. Is the target group NOT the superuser group? +
      + Presently, suEXEC does not allow the 'root' group to execute CGI/SSI programs. +
      +
      10. +
    10. Is the target groupid ABOVE the minimum ID number? +
      + The minimum group ID number is specified during configuration. This allows you + to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. + This is useful to block out "system" groups. +
      +
      11. +
    11. Can the wrapper successfully become the target user and group? +
      + Here is where the program becomes the target user and group via setuid and setgid + calls. The group access list is also initialized with all of the groups of which + the user is a member. +
      +
      12. +
    12. Does the directory in which the program resides exist? +
      + If it doesn't exist, it can't very well contain files. +
      +
      13. +
    13. Is the directory within the Apache webspace? +
      + If the request is for a regular portion of the server, is the requested directory + within the server's document root? If the request is for a UserDir, is the requested + directory within the user's document root? +
      +
      14. +
    14. Is the directory NOT writable by anyone else? +
      + We don't want to open up the directory to others; only the owner user may be able + to alter this directories contents. +
      +
      15. +
    15. Does the target program exist? +
      + If it doesn't exists, it can't very well be executed. +
      +
      16. +
    16. Is the target program NOT writable by anyone else? +
      + We don't want to give anyone other than the owner the ability to change the program. +
      +
      17. +
    17. Is the target program NOT setuid or setgid? +
      + We do not want to execute programs that will then change our UID/GID again. +
      +
      18. +
    18. Is the target user/group the same as the program's user/group? +
      + Is the user the owner of the file? +
      +
      19. +
    19. Can we successfully clean the process environment to ensure safe operations? +
      + suEXEC cleans the process' environment by establishing a safe execution PATH (defined + during configuration), as well as only passing through those variables whose names + are listed in the safe environment list (also created during configuration). +
      +
      20. +
    20. Can we successfully become the target program and execute? +
      + Here is where suEXEC ends and the target program begins. +
      +
      21. +

    @@ -257,7 +258,7 @@ section of this document. BACK TO CONTENTS

    -

    Configuring & Installing suEXEC

    +

    Configuring & Installing suEXEC

    Here's where we begin the fun. The configuration and installation of suEXEC is a four step process: edit the suEXEC header file, compile suEXEC, place the @@ -396,7 +397,7 @@ user shell, do so now and execute the following commands. BACK TO CONTENTS

    -

    Enabling & Disabling suEXEC

    +

    Enabling & Disabling suEXEC

    After properly installing the suexec wrapper executable, you must kill and restart the Apache server. A simple @@ -454,7 +455,7 @@ and the error_log for the server to see where you may have gone astray. BACK TO CONTENTS

    -

    Beware the Jabberwock: Warnings & Examples

    +

    Beware the Jabberwock: Warnings & Examples

    NOTE! This section may not be complete. For the latest revision of this section of the documentation, see the Apache Group's @@ -467,33 +468,33 @@ There are a few points of interest regarding the wrapper that can cause limitations on server setup. Please review these before submitting any "bugs" regarding suEXEC.

      - suEXEC Points Of Interest -
    • Hierarchy limitations -
      - 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 document root for - userdir requests. For example, if you have four VirtualHosts - configured, you would need to structure all of your VHosts' - document roots off of one main Apache document hierarchy to - take advantage of suEXEC for VirtualHosts. (Example forthcoming.) -
      -
      • -
    • suEXEC's PATH environment variable -
      - This can be a dangerous thing to change. Make certain every - path you include in this define is a trusted - directory. You don't want to open people up to having someone - from across the world running a trojan horse on them. -
      -
      • -
    • Altering the suEXEC code -
      - Again, this can cause Big Trouble if you try - this without knowing what you are doing. Stay away from it - if at all possible. -
      -
      • + suEXEC Points Of Interest +
    • Hierarchy limitations +
      + 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 document root for + userdir requests. For example, if you have four VirtualHosts + configured, you would need to structure all of your VHosts' + document roots off of one main Apache document hierarchy to + take advantage of suEXEC for VirtualHosts. (Example forthcoming.) +
      +
      • +
    • suEXEC's PATH environment variable +
      + This can be a dangerous thing to change. Make certain every + path you include in this define is a trusted + directory. You don't want to open people up to having someone + from across the world running a trojan horse on them. +
      +
      • +
    • Altering the suEXEC code +
      + Again, this can cause Big Trouble if you try + this without knowing what you are doing. Stay away from it + if at all possible. +
      +

    diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en index 7806bc8f55..0157cd0c1b 100644 --- a/docs/manual/suexec.html.en +++ b/docs/manual/suexec.html.en @@ -17,14 +17,15 @@

      - CONTENTS -
    1. What is suEXEC?
      2. -
    2. Before we begin.
      3. -
    3. suEXEC Security Model.
      4. -
    4. Configuring & Installing suEXEC
      5. -
    5. Enabling & Disabling suEXEC
      6. -
    6. Debugging suEXEC
      7. -
    7. Beware the Jabberwock: Warnings & Examples
      8. + CONTENTS +
    8. What is suEXEC?
      9. +
    9. Before we begin.
      10. +
    10. suEXEC Security Model.
      11. +
    11. Configuring & Installing suEXEC
      12. +
    12. Enabling & Disabling suEXEC
      13. +
    13. Debugging suEXEC
      14. +
    14. Beware the Jabberwock: Warnings & + Examples

    @@ -119,124 +120,124 @@ user and group IDs under which the program is to execute. The wrapper then employs the following process to determine success or failure -- if any one of these conditions fail, the program logs the failure and exits with an error, otherwise it will continue: -
      -
    1. Was the wrapper called with the proper number of arguments? -
      - The wrapper will only execute if it is given the proper number of arguments. - The proper argument format is known to the Apache web server. If the wrapper - is not receiving the proper number of arguments, it is either being hacked, or - there is something wrong with the suEXEC portion of your Apache binary. -
      -
      2. -
    2. Is the user executing this wrapper a valid user of this system? -
      - This is to ensure that the user executing the wrapper is truly a user of the system. -
      -
      3. -
    3. Is this valid user allowed to run the wrapper? -
      - Is this user the user allowed to run this wrapper? Only one user (the Apache - user) is allowed to execute this program. -
      -
      4. -
    4. Does the target program have an unsafe hierarchical reference? -
      - Does the target program contain a leading '/' or have a '..' backreference? These - are not allowed; the target program must reside within the Apache webspace. -
      -
      5. -
    5. Is the target user name valid? -
      - Does the target user exist? -
      -
      6. -
    6. Is the target group name valid? -
      - Does the target group exist? -
      -
      7. -
    7. Is the target user NOT superuser? -
      - Presently, suEXEC does not allow 'root' to execute CGI/SSI programs. -
      -
      8. -
    8. Is the target userid ABOVE the minimum ID number? -
      - The minimum user ID number is specified during configuration. This allows you - to set the lowest possible userid that will be allowed to execute CGI/SSI programs. - This is useful to block out "system" accounts. -
      -
      9. -
    9. Is the target group NOT the superuser group? -
      - Presently, suEXEC does not allow the 'root' group to execute CGI/SSI programs. -
      -
      10. -
    10. Is the target groupid ABOVE the minimum ID number? -
      - The minimum group ID number is specified during configuration. This allows you - to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. - This is useful to block out "system" groups. -
      -
      11. -
    11. Can the wrapper successfully become the target user and group? -
      - Here is where the program becomes the target user and group via setuid and setgid - calls. The group access list is also initialized with all of the groups of which - the user is a member. -
      -
      12. -
    12. Does the directory in which the program resides exist? -
      - If it doesn't exist, it can't very well contain files. -
      -
      13. -
    13. Is the directory within the Apache webspace? -
      - If the request is for a regular portion of the server, is the requested directory - within the server's document root? If the request is for a UserDir, is the requested - directory within the user's document root? -
      -
      14. -
    14. Is the directory NOT writable by anyone else? -
      - We don't want to open up the directory to others; only the owner user may be able - to alter this directories contents. -
      -
      15. -
    15. Does the target program exist? -
      - If it doesn't exists, it can't very well be executed. -
      -
      16. -
    16. Is the target program NOT writable by anyone else? -
      - We don't want to give anyone other than the owner the ability to change the program. -
      -
      17. -
    17. Is the target program NOT setuid or setgid? -
      - We do not want to execute programs that will then change our UID/GID again. -
      -
      18. -
    18. Is the target user/group the same as the program's user/group? -
      - Is the user the owner of the file? -
      -
      19. -
    19. Can we successfully clean the process environment to ensure safe operations? -
      - suEXEC cleans the process' environment by establishing a safe execution PATH (defined - during configuration), as well as only passing through those variables whose names - are listed in the safe environment list (also created during configuration). -
      -
      20. -
    20. Can we successfully become the target program and execute? -
      - Here is where suEXEC ends and the target program begins. -
      -
      21. -
    +
      +
    1. Was the wrapper called with the proper number of arguments? +
      + The wrapper will only execute if it is given the proper number of arguments. + The proper argument format is known to the Apache web server. If the wrapper + is not receiving the proper number of arguments, it is either being hacked, or + there is something wrong with the suEXEC portion of your Apache binary. +
      +
      2. +
    2. Is the user executing this wrapper a valid user of this system? +
      + This is to ensure that the user executing the wrapper is truly a user of the system. +
      +
      3. +
    3. Is this valid user allowed to run the wrapper? +
      + Is this user the user allowed to run this wrapper? Only one user (the Apache + user) is allowed to execute this program. +
      +
      4. +
    4. Does the target program have an unsafe hierarchical reference? +
      + Does the target program contain a leading '/' or have a '..' backreference? These + are not allowed; the target program must reside within the Apache webspace. +
      +
      5. +
    5. Is the target user name valid? +
      + Does the target user exist? +
      +
      6. +
    6. Is the target group name valid? +
      + Does the target group exist? +
      +
      7. +
    7. Is the target user NOT superuser? +
      + Presently, suEXEC does not allow 'root' to execute CGI/SSI programs. +
      +
      8. +
    8. Is the target userid ABOVE the minimum ID number? +
      + The minimum user ID number is specified during configuration. This allows you + to set the lowest possible userid that will be allowed to execute CGI/SSI programs. + This is useful to block out "system" accounts. +
      +
      9. +
    9. Is the target group NOT the superuser group? +
      + Presently, suEXEC does not allow the 'root' group to execute CGI/SSI programs. +
      +
      10. +
    10. Is the target groupid ABOVE the minimum ID number? +
      + The minimum group ID number is specified during configuration. This allows you + to set the lowest possible groupid that will be allowed to execute CGI/SSI programs. + This is useful to block out "system" groups. +
      +
      11. +
    11. Can the wrapper successfully become the target user and group? +
      + Here is where the program becomes the target user and group via setuid and setgid + calls. The group access list is also initialized with all of the groups of which + the user is a member. +
      +
      12. +
    12. Does the directory in which the program resides exist? +
      + If it doesn't exist, it can't very well contain files. +
      +
      13. +
    13. Is the directory within the Apache webspace? +
      + If the request is for a regular portion of the server, is the requested directory + within the server's document root? If the request is for a UserDir, is the requested + directory within the user's document root? +
      +
      14. +
    14. Is the directory NOT writable by anyone else? +
      + We don't want to open up the directory to others; only the owner user may be able + to alter this directories contents. +
      +
      15. +
    15. Does the target program exist? +
      + If it doesn't exists, it can't very well be executed. +
      +
      16. +
    16. Is the target program NOT writable by anyone else? +
      + We don't want to give anyone other than the owner the ability to change the program. +
      +
      17. +
    17. Is the target program NOT setuid or setgid? +
      + We do not want to execute programs that will then change our UID/GID again. +
      +
      18. +
    18. Is the target user/group the same as the program's user/group? +
      + Is the user the owner of the file? +
      +
      19. +
    19. Can we successfully clean the process environment to ensure safe operations? +
      + suEXEC cleans the process' environment by establishing a safe execution PATH (defined + during configuration), as well as only passing through those variables whose names + are listed in the safe environment list (also created during configuration). +
      +
      20. +
    20. Can we successfully become the target program and execute? +
      + Here is where suEXEC ends and the target program begins. +
      +
      21. +

    @@ -257,7 +258,7 @@ section of this document. BACK TO CONTENTS

    -

    Configuring & Installing suEXEC

    +

    Configuring & Installing suEXEC

    Here's where we begin the fun. The configuration and installation of suEXEC is a four step process: edit the suEXEC header file, compile suEXEC, place the @@ -396,7 +397,7 @@ user shell, do so now and execute the following commands. BACK TO CONTENTS

    -

    Enabling & Disabling suEXEC

    +

    Enabling & Disabling suEXEC

    After properly installing the suexec wrapper executable, you must kill and restart the Apache server. A simple @@ -454,7 +455,7 @@ and the error_log for the server to see where you may have gone astray. BACK TO CONTENTS

    -

    Beware the Jabberwock: Warnings & Examples

    +

    Beware the Jabberwock: Warnings & Examples

    NOTE! This section may not be complete. For the latest revision of this section of the documentation, see the Apache Group's @@ -467,33 +468,33 @@ There are a few points of interest regarding the wrapper that can cause limitations on server setup. Please review these before submitting any "bugs" regarding suEXEC.

      - suEXEC Points Of Interest -
    • Hierarchy limitations -
      - 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 document root for - userdir requests. For example, if you have four VirtualHosts - configured, you would need to structure all of your VHosts' - document roots off of one main Apache document hierarchy to - take advantage of suEXEC for VirtualHosts. (Example forthcoming.) -
      -
      • -
    • suEXEC's PATH environment variable -
      - This can be a dangerous thing to change. Make certain every - path you include in this define is a trusted - directory. You don't want to open people up to having someone - from across the world running a trojan horse on them. -
      -
      • -
    • Altering the suEXEC code -
      - Again, this can cause Big Trouble if you try - this without knowing what you are doing. Stay away from it - if at all possible. -
      -
      • + suEXEC Points Of Interest +
    • Hierarchy limitations +
      + 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 document root for + userdir requests. For example, if you have four VirtualHosts + configured, you would need to structure all of your VHosts' + document roots off of one main Apache document hierarchy to + take advantage of suEXEC for VirtualHosts. (Example forthcoming.) +
      +
      • +
    • suEXEC's PATH environment variable +
      + This can be a dangerous thing to change. Make certain every + path you include in this define is a trusted + directory. You don't want to open people up to having someone + from across the world running a trojan horse on them. +
      +
      • +
    • Altering the suEXEC code +
      + Again, this can cause Big Trouble if you try + this without knowing what you are doing. Stay away from it + if at all possible. +
      +

    -- 2.50.1