<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: question about inetd.sec in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889682#M281252</link>
    <description>umm, this isn't all that difficult to figure out.  The first sentence of the inetd.sec manpage states:&lt;BR /&gt;&lt;BR /&gt;"inetd.sec - optional security file for inetd"&lt;BR /&gt;&lt;BR /&gt;inetd.sec restricts access ONLY to inetd services in /etc/services and /etc/rpc; not to other services.</description>
    <pubDate>Wed, 01 Nov 2006 14:40:52 GMT</pubDate>
    <dc:creator>Bob Ingersoll</dc:creator>
    <dc:date>2006-11-01T14:40:52Z</dc:date>
    <item>
      <title>question about inetd.sec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889679#M281249</link>
      <description>usally I use inetd.sec to restrict some service about network,such as ftp and telnet,etc.&lt;BR /&gt;Now I have a question,does the inetd.sec can restrict all services list in /etc/services,or the inetd.sec only can restrict the service controlled by inetd.conf?&lt;BR /&gt;for example, if i want to restrict certain IP address to use database by inetd.sec,can I?</description>
      <pubDate>Tue, 31 Oct 2006 04:55:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889679#M281249</guid>
      <dc:creator>lin.chen</dc:creator>
      <dc:date>2006-10-31T04:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: question about inetd.sec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889680#M281250</link>
      <description>Hi lin.chen&lt;BR /&gt;&lt;BR /&gt;# man inetd.sec&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;Lines in inetd.sec beginning with # are comments.  Comments are not&lt;BR /&gt;      allowed at the end of a line of data.&lt;BR /&gt;&lt;BR /&gt;      The lines in the file contain a service name, permission field, and&lt;BR /&gt;      the Internet addresses or official names of the hosts and networks&lt;BR /&gt;      allowed to use that service in the local host.  The fields in each&lt;BR /&gt;      line are as follows:&lt;BR /&gt;&lt;BR /&gt;           &lt;SERVICE name=""&gt; &lt;ALLOW&gt; &lt;HOST&gt;&lt;BR /&gt;&lt;BR /&gt;      service name is the name (not alias) of a valid service in file&lt;BR /&gt;      /etc/services.  The service name for RPC-based services (NFS) is the&lt;BR /&gt;      name (not alias) of a valid service in file /etc/rpc.  A service name&lt;BR /&gt;      in /etc/rpc corresponds to a unique RPC program number.&lt;BR /&gt;&lt;BR /&gt;rgs,&lt;BR /&gt;&lt;BR /&gt;&lt;/HOST&gt;&lt;/ALLOW&gt;&lt;/SERVICE&gt;</description>
      <pubDate>Tue, 31 Oct 2006 05:05:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889680#M281250</guid>
      <dc:creator>rariasn</dc:creator>
      <dc:date>2006-10-31T05:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: question about inetd.sec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889681#M281251</link>
      <description>Hi,&lt;BR /&gt;the /etc/services file specifies ports and protocols allowed to connect. Once you have allowed a connection on a port and set up the service to handle the requests, you can use inetd.sec to control further security.&lt;BR /&gt;&lt;BR /&gt;Seem "man inetd.sec"&lt;BR /&gt;"The fields in each line are as follows:&lt;BR /&gt;&lt;BR /&gt;&lt;SERVICE name=""&gt; &lt;ALLOW&gt; &lt;HOST&gt;&lt;BR /&gt;&lt;BR /&gt;service name is the name (not alias) of a valid service in file /etc/services."&lt;/HOST&gt;&lt;/ALLOW&gt;&lt;/SERVICE&gt;</description>
      <pubDate>Tue, 31 Oct 2006 05:06:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889681#M281251</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-10-31T05:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: question about inetd.sec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889682#M281252</link>
      <description>umm, this isn't all that difficult to figure out.  The first sentence of the inetd.sec manpage states:&lt;BR /&gt;&lt;BR /&gt;"inetd.sec - optional security file for inetd"&lt;BR /&gt;&lt;BR /&gt;inetd.sec restricts access ONLY to inetd services in /etc/services and /etc/rpc; not to other services.</description>
      <pubDate>Wed, 01 Nov 2006 14:40:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-about-inetd-sec/m-p/3889682#M281252</guid>
      <dc:creator>Bob Ingersoll</dc:creator>
      <dc:date>2006-11-01T14:40:52Z</dc:date>
    </item>
  </channel>
</rss>

