<?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 RPC Security in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174030#M32131</link>
    <description>Hello all&lt;BR /&gt;After an intrusion detection session, the security team suggested som operation to perfomr on the RH AS4U4 box.&lt;BR /&gt;one of this is to disable the RPC service (ports 755/UDP and 758/TCP) if not used or allow access only to trusted host/networks.&lt;BR /&gt;&lt;BR /&gt;I cannot disable RPC service, but how to restrict access to a list of IPs and NETWORKs?&lt;BR /&gt;&lt;BR /&gt;Same issue for RPC lockmanager (1026/UDP).&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;RV</description>
    <pubDate>Fri, 04 Apr 2008 12:03:33 GMT</pubDate>
    <dc:creator>Roberto Volsa</dc:creator>
    <dc:date>2008-04-04T12:03:33Z</dc:date>
    <item>
      <title>RPC Security</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174030#M32131</link>
      <description>Hello all&lt;BR /&gt;After an intrusion detection session, the security team suggested som operation to perfomr on the RH AS4U4 box.&lt;BR /&gt;one of this is to disable the RPC service (ports 755/UDP and 758/TCP) if not used or allow access only to trusted host/networks.&lt;BR /&gt;&lt;BR /&gt;I cannot disable RPC service, but how to restrict access to a list of IPs and NETWORKs?&lt;BR /&gt;&lt;BR /&gt;Same issue for RPC lockmanager (1026/UDP).&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;RV</description>
      <pubDate>Fri, 04 Apr 2008 12:03:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174030#M32131</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2008-04-04T12:03:33Z</dc:date>
    </item>
    <item>
      <title>Re: RPC Security</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174031#M32132</link>
      <description>Using an iptables firewall would be your best option.</description>
      <pubDate>Fri, 04 Apr 2008 13:22:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174031#M32132</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-04-04T13:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: RPC Security</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174032#M32133</link>
      <description>I agree with Ivan on iptables, but there might be another option: many Linux distributions compile their RPC services with built-in libwrap support. &lt;BR /&gt;&lt;BR /&gt;Any libwrap-enabled services can be restricted using /etc/hosts.allow and /etc/hosts.deny, just like when using TCP wrappers on inetd services. Read the man page of your RPC service processes and/or the associated documentation in /usr/share/doc directory to find out if this is available.&lt;BR /&gt;&lt;BR /&gt;To get multiple layers of defense, you could of course use both iptables and libwrap features together.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 05 Apr 2008 11:37:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rpc-security/m-p/4174032#M32133</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-04-05T11:37:44Z</dc:date>
    </item>
  </channel>
</rss>

