Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual page 345

• — Logs the exit status or termination signal of the service (
EXIT
• — Logs the remote host's IP address (
HOST
• — Logs the process ID of the server receiving the request (
PID
• — Logs the remote user using the method defined in RFC 1413 for all multi-threaded
USERID
stream services (
log_on_failure
For a complete list of logging options, refer to the
4.3.2. Access Control Options
Users of services can choose to use the TCP wrappers hosts access rules, provide
xinetd
access control via the
the use of TCP wrappers hosts access control files can be found in
Configuration Files".
This section discusses using
Note
Unlike TCP wrappers, changes to access control only take effect if the
administrator restarts the
Also, unlike TCP wrappers, access control through
controlled by
The hosts access control differs from the method used by TCP wrappers. While TCP
xinetd
wrappers places all of the access configuration within two files,
,
/etc/hosts.deny xinetd
the directory.
/etc/xinetd.d/
The following hosts access options are supported by
• — Allows only the specified hosts to use the service.
only_from
• — Blocks listed hosts from using the service.
no_access
• — Specifies the time range when a particular service may be used. The time
access_times
range must be stated in 24-hour format notation,
The and
only_from no_access
specify an entire network. Like TCP wrappers, combining
enhanced logging configuration can increase security by blocking requests from banned hosts
while verbosely recording each connection attempt.
and
log_on_success
configuration files, or a mixture of both. Information concerning
xinetd
to control access to services.
xinetd
xinetd
.
xinetd
's access control is found in each service's configuration file within
options can use a list of IP addresses or host names, or can
Altering
xinetd
log_on_success
and
log_on_failure
log_on_success
).
man page.
xinetd.conf
Section 2, "TCP Wrappers
service.
xinetd
/etc/hosts.allow
:
xinetd
.
HH:MM-HH:MM
access control with the
xinetd
Configuration Files
).
).
log_on_success
).
xinetd
only affects services
and
321