<?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 Securing RPC-based services - Inetd.sec vs IPFilter in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269565#M178381</link>
    <description>Is there a way to use IPFilter (A.03.05.09) to restrict (by IP address) the use of individual RPC-based services in /etc/rpc or do I need to use the inetd.sec file?</description>
    <pubDate>Thu, 06 May 2004 09:00:37 GMT</pubDate>
    <dc:creator>Robert C. Hursch</dc:creator>
    <dc:date>2004-05-06T09:00:37Z</dc:date>
    <item>
      <title>Securing RPC-based services - Inetd.sec vs IPFilter</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269565#M178381</link>
      <description>Is there a way to use IPFilter (A.03.05.09) to restrict (by IP address) the use of individual RPC-based services in /etc/rpc or do I need to use the inetd.sec file?</description>
      <pubDate>Thu, 06 May 2004 09:00:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269565#M178381</guid>
      <dc:creator>Robert C. Hursch</dc:creator>
      <dc:date>2004-05-06T09:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: Securing RPC-based services - Inetd.sec vs IPFilter</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269566#M178382</link>
      <description>&lt;BR /&gt;You can allow/deny access to ports related to an IP via ipfilter.&lt;BR /&gt; &lt;BR /&gt;&lt;A href="http://www.obfuscation.org/ipf/ipf-howto.txt" target="_blank"&gt;http://www.obfuscation.org/ipf/ipf-howto.txt&lt;/A&gt;&lt;BR /&gt; &lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Thu, 06 May 2004 09:31:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269566#M178382</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2004-05-06T09:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: Securing RPC-based services - Inetd.sec vs IPFilter</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269567#M178383</link>
      <description>I have seen this document that you refer to and it does describe securing ports, but I could not find details about coding the /etc/rpc "program numbers" into my ipf.conf file.  Could I code the number 100017 from /etc/rpc to restrict access for the rexd usage?  Thanks</description>
      <pubDate>Thu, 06 May 2004 10:00:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/securing-rpc-based-services-inetd-sec-vs-ipfilter/m-p/3269567#M178383</guid>
      <dc:creator>Robert C. Hursch</dc:creator>
      <dc:date>2004-05-06T10:00:43Z</dc:date>
    </item>
  </channel>
</rss>

