Home > Articles > Operating Systems, Server > Linux/UNIX/Open Source

Security Tools

  • Print
  • + Share This
Like this article? We recommend

Xinetd

Xinetd is designed to be a secure replacement for the inetd program. It provides a more secure method for providing access to Internet services through a master daemon along with a number of other useful facilities. Xinetd was originally written by Panagiotis Tsirigotis. Currently, it is maintained by Rob Braun. It is supported by a Web page at http://www.xinetd.org and a mailing list hosted at synack.net.

Xinetd, like inetd, runs as a "super-server," or a switchboard. It listens on a number of ports and starts daemons as appropriate for incoming requests. Xinetd goes beyond the functionality of inetd in many ways. It takes advantage of its role as a switchboard operator to do a variety of things before it ever hands control off to the application daemon. Some of this functionality is used to create a more secure environment; other bits just make life better (or easier) for you, the administrator.

One of the most common tasks Xinetd performs is access control. Connections to a host can be allowed or disallowed based on the domain, name, or address of the remote host, and/or the time of access. If desired, Xinetd can be compiled with lib-wrap support to use the hosts.allow and hosts.deny files. Xinetd even allows you to bind specific services to specific IP addresses.

Xinetd is also used to prevent denial of services (DoS) attacks. Because it is looking at all the connections into a host instead of just one connection, Xinetd can limit the number of connections to given services. You can also set connection limits based on distinct client hosts.

One of the real strengths of Xinetd is its extensive logging capability. You can configure logging for each service individually. If you want to avoid syslog, you can write logs to log files directly. You can log information about failed connection attempts. You can even use Xinetd to log the connect and disconnect times of each connection.

Xinetd allows you to redirect TCP connections to a different host. These connections continue to run through the original host, so you could use this functionality to provide services from a privately addressed machine to the Internet.

Getting and Installing xinetd

Xinetd is now part of a stock Red Hat 7 system, but getting and building it is pretty straightforward as well. The sources are available from http://www.xinetd.org. There are currently two flavors: the stable release and the development release. Make sure that you grab the stable release.

Building Xinetd follows the normal configure, make, make install procedure. On a Red Hat 6.2 system it built and installed without any errors. If you do run into problems, please try the mailing list (see the section "What If I Have Problems" for information about subscribing).

The extra functionality provided by Xinetd means that it needs more information in its configuration file than inetd does. The two file formats are not interchangeable. A tool is provided to convert your existing /etc/inetd.conf, though, so things are relatively painless. To perform the conversion, do the following:

[root@cherry sbin]$ ./xconv.pl < inetd.conf > /etc/xinetd.conf

The resulting file is probably not exactly what you want, but it should work. The next section deals with making Xinetd do what you want it to.

Xinetd at Work

We'll take a small inetd.conf file and run it through xconv.pl to come up with a basic xinetd.conf. From there, we'll make incremental changes to our xinetd.conf to get it into shape for our own network.

A Basic Configuration

We'll start with a very short inetd.conf file, as shown in Listing 5.

Listing 5 A Basic inetd.conf

echo  stream tcp nowait root internal
echo  dgram  udp wait  root internal
ftp   stream tcp nowait root /usr/sbin/in.ftpd in.ftpd -l -a
telnet stream tcp nowait root /usr/sbin/in.telnetd    in.telnetd
imap  stream tcp nowait root /usr/sbin/imapd imapd
finger stream tcp nowait nobody
[ccc] /usr/local/sbin/my_safe.fingerd in.fingerd

This config file only runs four external services on an internal service to the TCP protocol. After running xconv.pl on it, we get the xinetd.conf file shown in Listing 6.

Listing 6 The Converted xinetd.conf

# The file is merely a translation of your inetd.conf file into
# the equivalent in xinetd.conf syntax. xinetd has many
# features that may not be taken advantage of with this translation.

# The defaults section sets some information for all services
defaults
{
   # The maximum number of requests a particular service may handle
   # at once.
   instances = 25

   # The type of logging. This logs to a file that is specified.
   # Another option is: SYSLOG syslog_facility [syslog_level]
   log_type  = FILE /var/log/servicelog

   # What to log when the connection succeeds.
   # PID logs the pid of the server processing the request.
   # HOST logs the remote host's ip address.
   # USERID logs the remote user (using RFC 1413)
   # EXIT logs the exit status of the server.
   # DURATION logs the duration of the session.
   log_on_success = HOST PID

   # What to log when the connection fails. Same options as above
   log_on_failure = HOST RECORD

   # The maximum number of connections a specific IP address can
   # have to a specific service.
   per_source = 5
}

service echo
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   type     = INTERNAL
   id      = echo-stream
}
service ftp
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   server    = /usr/sbin/in.ftpd
   server_args = in.ftpd -l -a
}
service telnet
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   server    = /usr/sbin/in.telnetd
   server_args = in.telnetd
}
service imap
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   server    = /usr/sbin/imapd
   server_args = imapd
}
service finger
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = nobody
   server    = /usr/local/sbin/my_safe.fingerd
   server_args = my_safe.fingerd
}

This config file really doesn't do everything we want it to, so we'll make some changes to it. First, we only want 1 ftp connection at a time. Second, we're only going to allow telnet sessions from internal hosts (they'll have 192.168.1.0/24 addresses).We'll log all finger connections and connect them to /usr/local/my_safe.fingerd. Because we're not running imap on this host, we'll redirect all imap sessions to our imap server at 192.168.1.10.

Throttling ftp connections is fairly straightforward. We'll modify the ftp section to look like that shown in Listing 7.

Listing 7 Defining ftp

service ftp
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   server    = /usr/sbin/in.ftpd
   server_args = in.ftpd -l -a
   instances  = 1
}

Controlling access is also straightforward. We'll modify the telnet session to match Listing 8.

Listing 8 Defining Access Control for telnet

service telnet
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   server    = /usr/sbin/in.telnetd
   server_args = in.telnetd
   only_from  = 192.168.1.0/24
}

What if we wanted to disallow connection from hosts within our local subnet during non-work hours? The following line could be added at the end of the section (after the only_from line):

access_time =08:00-18:00

Similarly, you could disallow certain connections all the time by adding the rule:

# this guy is trouble
  no_access =192.168.1.20

We're logging information by default, but we're going to try and capture extra information about finger users. Listing 9 shows how to do this.

Listing 9 Capturing finger Data

service finger
{
   flags     = REUSE NAMEINARGS
   socket_type  = stream
   protocol    = tcp
   wait      = no
   user      = nobody
   server     = /usr/local/sbin/my_safe.fingerd
   server_args  = my_safe.fingerd
   log_on_success = PID HOST USERID
}

Finally, to redirect imap users to the right place, we'll make the changes shown in Listing 10.

Listing 10 Redirect imap Users

service imap
{
   flags    = REUSE NAMEINARGS
   socket_type = stream
   protocol   = tcp
   wait     = no
   user     = root
   redirect   = 192.168.1.10 143
}

What If I Have Problems?

If you run into problems in installing, setting up, or using Xinetd, you should subscribe to the mailing list and ask for help.2 You can subscribe by sending mail to majordomo@synack.net with a body of "subscribe xinetd".

If You Subscribe

When there, please try to make a good bug report. Be specific, include all the pertinent information, and be polite! Remember that the folks who will be answering your questions are just folks volunteering their time. They will get annoyed, and might ignore you entirely if you can't be bothered to write a decent note describing your problem, what you've done, and indicating that you've at least tried to read the docs.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020