<?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: Linux .rhosts /etc/hosts.equiv in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760801#M88680</link>
    <description>If these machines are exosed on the Internet, make sure you have ipchains firewall on the Linux side.&lt;BR /&gt;&lt;BR /&gt;On the HP-UX side /hosts.equiv overrides .rhosts files, brings things under administrators control.  With a /var/adm/inetd.sec file you can restrict users by network address(only 10.1.10 for example) and protocol. You can and should stop telnet, and be choosey about what other protocols you let through.&lt;BR /&gt;&lt;BR /&gt;I highly recommend this for the HP-UX side otherwise the world can get on your HP-UX box.</description>
    <pubDate>Fri, 23 Aug 2002 18:23:02 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2002-08-23T18:23:02Z</dc:date>
    <item>
      <title>Linux .rhosts /etc/hosts.equiv</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760798#M88677</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;i want to alloy any user on host a to rsh to host b as user dummy.&lt;BR /&gt;In other OS i can put '+' in ~.rhosts for the username.&lt;BR /&gt;In RH Linux i have to put every username in ~.rhosts if it should work.&lt;BR /&gt;But i need a solution that any user on host a (Hp-UX) may do a remsh host_a -l dummy. (remote shell only for user dummy and not more !)&lt;BR /&gt;ssh isn't a solution because the applications uses rsh (remsh)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Jul 2002 08:38:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760798#M88677</guid>
      <dc:creator>Stefan Marquardt_1</dc:creator>
      <dc:date>2002-07-10T08:38:06Z</dc:date>
    </item>
    <item>
      <title>Re: Linux .rhosts /etc/hosts.equiv</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760799#M88678</link>
      <description>Won't /etc/hosts.equiv allow this?&lt;BR /&gt;&lt;BR /&gt;man hosts.equiv for more detail.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Thu, 11 Jul 2002 00:28:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760799#M88678</guid>
      <dc:creator>Mark Fenton</dc:creator>
      <dc:date>2002-07-11T00:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: Linux .rhosts /etc/hosts.equiv</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760800#M88679</link>
      <description>The error wasn't the rhosts file or hosts.equiv.&lt;BR /&gt;&lt;BR /&gt;server + is o.k. but the "+" isnt't enabled default on RH 7.1 ...&lt;BR /&gt;Solution:&lt;BR /&gt;Edit /etc/pam.d/rsh&lt;BR /&gt;Add promiscuous after pam_rhosts_auth.so&lt;BR /&gt;&lt;BR /&gt;man pages for rhosts and hosts.equiv aren't helpful.&lt;BR /&gt;The Pam Admin Doc helps.&lt;BR /&gt;</description>
      <pubDate>Thu, 11 Jul 2002 07:30:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760800#M88679</guid>
      <dc:creator>Stefan Marquardt_1</dc:creator>
      <dc:date>2002-07-11T07:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Linux .rhosts /etc/hosts.equiv</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760801#M88680</link>
      <description>If these machines are exosed on the Internet, make sure you have ipchains firewall on the Linux side.&lt;BR /&gt;&lt;BR /&gt;On the HP-UX side /hosts.equiv overrides .rhosts files, brings things under administrators control.  With a /var/adm/inetd.sec file you can restrict users by network address(only 10.1.10 for example) and protocol. You can and should stop telnet, and be choosey about what other protocols you let through.&lt;BR /&gt;&lt;BR /&gt;I highly recommend this for the HP-UX side otherwise the world can get on your HP-UX box.</description>
      <pubDate>Fri, 23 Aug 2002 18:23:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-rhosts-etc-hosts-equiv/m-p/2760801#M88680</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2002-08-23T18:23:02Z</dc:date>
    </item>
  </channel>
</rss>

