From 1569974707caf18a0bf85ca807ff1b52074f68ab Mon Sep 17 00:00:00 2001 From: Vincent Bray Date: Thu, 13 Nov 2008 00:53:09 +0000 Subject: [PATCH] Initial build of mod_unixd.html* plus props git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@713590 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_unixd.html | 5 + docs/manual/mod/mod_unixd.html.en | 162 ++++++++++++++++++++++++++++++ 2 files changed, 167 insertions(+) create mode 100644 docs/manual/mod/mod_unixd.html create mode 100644 docs/manual/mod/mod_unixd.html.en diff --git a/docs/manual/mod/mod_unixd.html b/docs/manual/mod/mod_unixd.html new file mode 100644 index 0000000000..b1ecd73183 --- /dev/null +++ b/docs/manual/mod/mod_unixd.html @@ -0,0 +1,5 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: mod_unixd.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_unixd.html.en b/docs/manual/mod/mod_unixd.html.en new file mode 100644 index 0000000000..35d92da9ed --- /dev/null +++ b/docs/manual/mod/mod_unixd.html.en @@ -0,0 +1,162 @@ + + + +mod_unixd - Apache HTTP Server + + + + + + +
<-
+
+Apache > HTTP Server > Documentation > Version 2.3 > Modules
+
+

Apache Core Features

+
+

Available Languages:  en 

+
+ +
Description:Basic (required) security for Unix-family platforms.
Status:Core
+
+

Directives

+ +
+ +
top
+

ChrootDir Directive

+ + + + + + + +
Description:Directory for apache to run chroot(8) after startup.
Syntax:ChrootDir /path/to/directory
Default:none
Context:server config
Status:Core
Module:event, prefork, worker
+

This directive, available in httpd 2.2.9(?) and later, tells the + server to chroot(8) to the specified directory after + startup, but before accepting requests over the 'net.

+

Note that running the server under chroot is not simple, + and requires additional setup, particularly if you are running + scripts such as CGI or PHP. Please make sure you are properly + familiar with the operation of chroot before attempting to use + this feature.

+ +
+
top
+

Group Directive

+ + + + + + + + +
Description:Group under which the server will answer +requests
Syntax:Group unix-group
Default:Group #-1
Context:server config
Status:Core
Module:mod_unixd
Compatibility:Only valid in global server config since Apache +2.0
+

The Group directive sets the group under + which the server will answer requests. In order to use this + directive, the server must be run initially as root. If + you start the server as a non-root user, it will fail to change to the + specified group, and will instead continue to run as the group of the + original user. Unix-group is one of:

+ +
+
A group name
+
Refers to the given group by name.
+ +
# followed by a group number.
+
Refers to a group by its number.
+
+ +

Example

+ Group www-group +

+ +

It is recommended that you set up a new group specifically for + running the server. Some admins use user nobody, + but this is not always possible or desirable.

+ +

Security

+

Don't set Group (or User) to root unless + you know exactly what you are doing, and what the dangers are.

+
+ + +

See also

+ +
+
top
+

User Directive

+ + + + + + + + +
Description:The userid under which the server will answer +requests
Syntax:User unix-userid
Default:User #-1
Context:server config
Status:Core
Module:mod_unixd
Compatibility:Only valid in global server config since Apache +2.0
+

The User directive sets the user ID as + which the server will answer requests. In order to use this + directive, the server must be run initially as root. + If you start the server as a non-root user, it will fail to change + to the lesser privileged user, and will instead continue to run as + that original user. If you do start the server as root, + then it is normal for the parent process to remain running as root. + Unix-userid is one of:

+ +
+
A username
+
Refers to the given user by name.
+ +
# followed by a user number.
+
Refers to a user by its number.
+
+ +

The user should have no privileges that result in it being + able to access files that are not intended to be visible to the + outside world, and similarly, the user should not be able to + execute code that is not meant for HTTP requests. It is + recommended that you set up a new user and group specifically for + running the server. Some admins use user nobody, but + this is not always desirable, since the nobody user + can have other uses on the system.

+ +

Security

+

Don't set User (or Group) to root unless + you know exactly what you are doing, and what the dangers are.

+
+ + +

See also

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file -- 2.40.0