Network Services connection should be allowed, then starts the appropriate server (if required) to handle the connection. In this section, we’ll take a brief look at some of the configuration options xinetd has that relate to system security. xinetd’s main configuration file is /etc/xinetd.conf. Let’s have a look at that now: This file simply sets up some sensible default values that apply to all services managed by xinetd (by placing them inside defaults {} ), then tells xinetd to read configuration information from all the files in /etc/xinetd.d. The default values have the following meanings: instances = 60 No more than 60 instances of each sub-server will be started logtype = SYSLOG authpriv Service log output is sent to syslogd using the authpriv facility (so that the output is logged to a file that can only be read by privileged users) log_on_success = HOST PID Logs remote host address and process id (if there is one) when a service is started or exits log_on_failure = HOST Logs remote host address when a service failed to start (with the reason for the failure) cps = 25 30 Allows maximum connection rate of 25 connections per second (first number) and disable service for 30 seconds (second number) if this rate is exceeded Monitoring Services It is useful to be able to check what services are running on our Red Hat Linux 9 system, and especially what ports they are listening on. This is because before a remote machine can make a connection to our local machine, some process on our local machine has to be ready to receive network packets (listening) sent to its port number. There are a couple of tools that we can use to identify what ports are listening on our machine: netstat and nmap. netstat Netstat is a multipurpose utility for reporting on all things relating to networks. We’ll invoke it with the following flags: Flag Meaning -t TCP 419

Hint: This post is supported by Gama web hosting php services