HostsAllowSyslogLevel

HostsAllowSyslogLevel adjusts the verbosity of the messages recorded in the error logs by mod_wrap, particularly for allowed connections. The following levels are available, in order of decreasing significance:

Level Description
emerg Emergencies - system is unusable.
alert Action must be taken immediately.
crit Critical Conditions.
error Error conditions.
warn Warning conditions.
notice Normal but significant condition.
info Informational.
debug Debug-level messages

Level	Description
`emerg`	Emergencies - system is unusable.
`alert`	Action must be taken immediately.
`crit`	Critical Conditions.
`error`	Error conditions.
`warn`	Warning conditions.
`notice`	Normal but significant condition.
`info`	Informational.
`debug`	Debug-level messages

Using a level of info is recommended.

HostsDenySyslogLevel

HostsDenySyslogLevel adjusts the verbosity of the messages recorded in the error logs by mod_wrap, specifically for denied connections. The following levels are available, in order of decreasing significance:

Level	Description
`emerg`	Emergencies - system is unusable.
`alert`	Action must be taken immediately.
`crit`	Critical Conditions.
`error`	Error conditions.
`warn`	Warning conditions.
`notice`	Normal but significant condition.
`info`	Informational.
`debug`	Debug-level messages

Using a level of warn is recommended.

UseHostsAllowFile

Syntax: UseHostsAllowFile [path]
Default: None
Context: server config, <VirtualHost>, <Anonymous>
Module: mod_wrap
Compatibility: 1.2.0rc2 and later

The UseHostsAllowFile directive causes TCP wrappers-like access control to be used. The path argument is optional; if not provided, mod_wrap will default to looking at /etc/hosts.allow as the allow file. If a path is given, then mod_wrap will use the given path as the allow file. mod_wrap checks for a listing for "proftpd" in the allow file.

The path, if provided, must start with either a "/" or a "~". If it starts with a "/", or if it starts with a "~" and is followed by a user name, mod_wrap will check that it's a usable file (ie the file exists and is readable) at start-up time. If, however, the path starts with a "~" and is not followed by a user name, the check is done at login time.

For example:

  UseHostsAllowFile ~/my.allow

will cause mod_wrap to check for the file "my.allow" in the home directory of the logging-in user.

If the allow or the deny file specified is unusable, or if only one of these files has been configured, then mod_wrap will not check the connection request - both files are necessary for the access check.

Further reading for the use of the TCP wrapper files can be found in the hosts_access(3) and hosts_access(5) man pages.

UseHostsDenyFile

Syntax: UseHostsDenyFile [path]
Default: None
Context: server config, <VirtualHost>, <Anonymous>
Module: mod_wrap
Compatibility: 1.2.0rc2 and later

The UseHostsDenyFile directive causes TCP wrappers-like access control to be used. The path argument is optional; if not provided, mod_wrap will default to looking at /etc/hosts.deny as the deny file. If a path is given, then mod_wrap will use the given path as the deny file. mod_wrap checks for a listing for "proftpd" in the deny file.

  UseHostsDenyFile ~/my.deny

will cause mod_wrap to check for the file "my.deny" in the home directory of the logging-in user.

Further reading for the use of the TCP wrapper files can be found in the hosts_access(3) and hosts_access(5) man pages.