On Tue, 30 May 2000, Alan Mead wrote:
> At 01:53 PM 5/30/00 , Carey F. Cox wrote:
> >Anyway, do the following
> >
> > 1) Check to make sure /etc/hosts.equiv has the client ip addresses.
>
> I need to put something in /etc/hosts.equiv? Or do you mean /etc/hosts? I
> can try modifying .equiv when I get home this eve but I didn't have root
> access in the past when I used .rhosts files and I don't think the sys
> admin happened to have the other computer in his .equiv file...
>
> The entries do appear in /etc/hosts
I quote from the rshd manpage...
"Rshd then validates the user using ruserok(3), which uses the file
/etc/hosts.equiv and the .rhosts file found in the user's home directory."
It gives a list of one hostname or ip address per line, i.e.
foo
foo.bar.hom
192.168.0.1
>
> > 2) Uncomment the following line in /etc/inetd.conf ...
> >
> >#shell stream tcp nowait root /usr/sbin/tcpd in.rshd
> >
> > 3) Restart tcp wrappers via
> >
> > /etc/rc.d/init.d/inet stop
> > /etc/rc.d/init.d/inet start
>
> Did this, in fact I see that rsh goes to rlogin when no command is given so
> I uncommented that and, in desperation, the rexec service as well. And
> restarted inetd.
Oops, forgot about rlogin, etc.
>
>
> >That should do it. If you have problems after that, check the permissions on
> >.rhosts.
>
> This I did not check. What permissions do I need? I didn't see any
> warnings or errors in the logs.
I extrapolating here, but for ssh, the .shosts file must be writable only
by the user (not even group) and must be world readable.
Carey
--
======================================================================
<> Carey F. Cox, PhD | PHONE: (409) 880-8770 <>
<> Assistant Professor | FAX: (409) 880-8121 <>
<> Dept. of Mech. Eng. | EMAIL: [EMAIL PROTECTED] <>
<> Lamar University | WEB: N/A <>
======================================================================
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
