According to the man pages and my own experience, /.rhosts entries that
look like this
systemname root
will grant root access to root users coming from the named system with
rsh, rcp, rlogin, rdist, etc.
I have tried relentlessly to get this to work, both systems on the same
subnet, various tries with and without fully-qualified hostnames,
checked /etc/hosts for consistency in the hostnames, etc. etc. and it
still doesn't grant access without asking for a password.
Help! Do I need a patch or is there some file I am forgetting?
(/etc/hosts.equiv is the only one I can see that would otherwise affect
rhosts, but it's apparently not checked for root access)
thanks,
trey
>According to the man pages and my own experience, /.rhosts entries that
>look like this
>systemname root
>will grant root access to root users coming from the named system with
>rsh, rcp, rlogin, rdist, etc.
You should be able to gain access with 'rsh command', with 'rcp' and
with 'rdist'. For 'rlogin' you have the additional problem that root
is only allowed to login from the console unless you change the
restrict specified in '/etc/default/login'.
I'll take a stab at this, since no one has. I recently had a similar
situation, where it looked like .rhosts wouldn't work. The cause
was the hostname getting passed from one system to another - sometimes
it was coming across as the full DNS hostname, other times the
full NIS+ hostname, other times just the plain hostname. SunSolve
had a workaround: if you rlogin from one host to another, then do
a "who am i", it will show you the host name that's getting passed.
Put this in .rhosts and all should be okay. I ended up adding all
possible permutations for the hostnames in question.
Hope this works.
--
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Joe Pawlicki - Unix Systems Administrator - U S WEST
jpa...@uswest.com ...my hovercraft is full of eels...
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/