<?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: configure rsh in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572816#M89554</link>
    <description>Hi &lt;BR /&gt;You need .rhosts file for it. add the system name from where you are doing rsh&lt;BR /&gt;For example rsh from server1 to server2 as a root&lt;BR /&gt;&lt;BR /&gt;add /root/.rhosts file and add server1 in it&lt;BR /&gt;&lt;BR /&gt;It should work. you don't even need hosts.allow file.&lt;BR /&gt;&lt;BR /&gt;Sachin</description>
    <pubDate>Thu, 30 Aug 2001 15:24:13 GMT</pubDate>
    <dc:creator>Sachin Patel</dc:creator>
    <dc:date>2001-08-30T15:24:13Z</dc:date>
    <item>
      <title>configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572815#M89553</link>
      <description>I am running RH7.1, I've have taken step to turn rsh on by enabling it in /etc/xinetd.d. I've also put the address of the remote server in /etc/hosts.equiv however when I did an rsh from the remote host, it's still asking me for a password.  Does any know how to open rsh up without prompting for a password.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Thu, 30 Aug 2001 13:19:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572815#M89553</guid>
      <dc:creator>Michael Chan_3</dc:creator>
      <dc:date>2001-08-30T13:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572816#M89554</link>
      <description>Hi &lt;BR /&gt;You need .rhosts file for it. add the system name from where you are doing rsh&lt;BR /&gt;For example rsh from server1 to server2 as a root&lt;BR /&gt;&lt;BR /&gt;add /root/.rhosts file and add server1 in it&lt;BR /&gt;&lt;BR /&gt;It should work. you don't even need hosts.allow file.&lt;BR /&gt;&lt;BR /&gt;Sachin</description>
      <pubDate>Thu, 30 Aug 2001 15:24:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572816#M89554</guid>
      <dc:creator>Sachin Patel</dc:creator>
      <dc:date>2001-08-30T15:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572817#M89555</link>
      <description>Don't forget, when you are doing rsh being root, to either remove "securettys" lines in pam configuration, or to remove /etc/securetty file.&lt;BR /&gt;Otherwise, it would work for any user, except root.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jerome</description>
      <pubDate>Thu, 30 Aug 2001 17:13:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572817#M89555</guid>
      <dc:creator>Jerome Fenal_1</dc:creator>
      <dc:date>2001-08-30T17:13:51Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572818#M89556</link>
      <description>that's nice guys, but I want to be able to control who can rsh in and that's why I need /etc/hosts.allow because I've denied access in /etc/deny.allow, I've also had the name of the remote host in ~/.rhosts file. when rsh from remote host, it asks me for a password.  &lt;BR /&gt;&lt;BR /&gt;As for as root is concerned I already had it working with /etc/securettty in place.  The trick to include rsh in it. Removing /etc/securetty is not a good idea.  It's put in there for a purpose.  I know openning rsh is not a good practice either, but I need it for budtools app. This why I need to put restrictions on the who can rsh in. For this purpose, I got the job done with rsh using root as the user to do my backup. But for education purposes, how can I do this for the regular user?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Thu, 30 Aug 2001 18:51:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572818#M89556</guid>
      <dc:creator>Michael Chan_3</dc:creator>
      <dc:date>2001-08-30T18:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572819#M89557</link>
      <description>if you are also using pam, you may need to take a look at /etc/pam.d/rsh .&lt;BR /&gt;&lt;BR /&gt;The entry you are looking for, I believe, would be &lt;BR /&gt;auth sufficient  /lib/security/pam_rhosts_auth.so&lt;BR /&gt;&lt;BR /&gt;if you don't want auth to ask for a passwd...</description>
      <pubDate>Fri, 31 Aug 2001 00:57:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572819#M89557</guid>
      <dc:creator>Mark Fenton</dc:creator>
      <dc:date>2001-08-31T00:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572820#M89558</link>
      <description>Hi kc,&lt;BR /&gt;&lt;BR /&gt;A agree with Sachin, but you need also to set owner:group for the $HOME/.rhosts&lt;BR /&gt;&lt;BR /&gt;Example "Remote shell from server1  to server 2" :&lt;BR /&gt;&lt;BR /&gt;1. Create, on server2,  the file ".rhosts" in the home directory that you want a specific user to use the remote shell command. And put inside the server from which the remote command will be issued, like :&lt;BR /&gt;&lt;BR /&gt;server1  +&lt;BR /&gt;&lt;BR /&gt;2. Set permission to 400 on file .rhosts on server2:&lt;BR /&gt;#chmod 400 $HOME/.rhosts&lt;BR /&gt;&lt;BR /&gt;3. chown userName:groupNmae .rhosts&lt;BR /&gt;&lt;BR /&gt;Now, userName can issue remote shell commands from server1 to server2.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Magdi</description>
      <pubDate>Fri, 31 Aug 2001 15:14:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572820#M89558</guid>
      <dc:creator>Magdi KAMAL</dc:creator>
      <dc:date>2001-08-31T15:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572821#M89559</link>
      <description>If it is still not working, one thing to check is:&lt;BR /&gt;&lt;BR /&gt;telnet to target server from remote host. On target host do "who -u" to see what machine name is displayed. Make sure the machine name matches what is in .rhosts.</description>
      <pubDate>Fri, 31 Aug 2001 16:43:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572821#M89559</guid>
      <dc:creator>Gary Seibak</dc:creator>
      <dc:date>2001-08-31T16:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572822#M89560</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I can't remember all the details, but there were an issue with some versions of rsh (the one I had problems with was shipped with RH7.0). To solve the problem, I had to re-install rsh from another RPM package.&lt;BR /&gt;&lt;BR /&gt;Try something like this.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Kodjo&lt;BR /&gt;</description>
      <pubDate>Fri, 31 Aug 2001 19:00:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572822#M89560</guid>
      <dc:creator>Kodjo Agbenu</dc:creator>
      <dc:date>2001-08-31T19:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: configure rsh</title>
      <link>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572823#M89561</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What you need to do in addition to the .rhosts issue which was mentioned here is to add the word promiscuous to the /etc/pam.d/rsh file like the following :&lt;BR /&gt;auth    required /lib/security/pam_rhosts_auth.so promiscuous&lt;BR /&gt;&lt;BR /&gt;for rlogin there's a seperate file under /etc/pam.d&lt;BR /&gt;&lt;BR /&gt;For root automatic rlogin you need to do additional thing like add the name of the service that you want to the /etc/securetty ( rlogin,rsh .. )&lt;BR /&gt;</description>
      <pubDate>Sat, 01 Sep 2001 07:14:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/configure-rsh/m-p/2572823#M89561</guid>
      <dc:creator>Zeev Fisher</dc:creator>
      <dc:date>2001-09-01T07:14:08Z</dc:date>
    </item>
  </channel>
</rss>

