On Sun May 03 1998, [EMAIL PROTECTED] wrote:
> At 12:04 AM 5/3/98 -0300, you wrote:
[I missed the original post.]
> >Sorry for this question, but this _silly_ thing is driving me mad.
> >Can anyone tell me why I cannot make rlogin, rsh, rcp, and the like work.
They should work like a charm. They do for me (and on mixed unix systems
at each end).
> >I've made the same user on both linux systems and then put the .rhosts
> >file in the home directory, but it doesn't work. I've made this many
> >times on Solaris and SCO systems but does linux have something else??,
> >I'm very frustrated. :-(
First thing to do (for security) is:
% chmod 600 ~/.rhosts
In fact, I'm under the impression that some (all?) of the linux
implementations of rlogind/rshd/rcpd/etc won't work if an .rhosts file is
readable by anyone else but the user. (I may be wrong, but I'm lazy and
can't be bothered to check:)
The ~/.rhosts file itself consists of:
remotehost.some.where username_at_remotehost
Usernames don't need to be identical, but the login name on the machine you
are coming in from must be specified. It works just fine if you use (at the
client/local machine) the `-l' option to rlogin and specify a
[EMAIL PROTECTED] for rcp and rsh.
> Are these services enabled in /etc/inetd.conf ?
Good question. If these lines are commented out, then uncomment them.
Then send a `kill -HUP' signal to your inetd daemon to get it to re-read
it.
Also, if tcp wrappers (/usr/sbin/tcpd) is being used (and it should be),
then make sure that the files /etc/hosts.{allow,deny,equiv} are not
preventing it from working like you expect.
Also check to see if there's a router somewhere running a firewall that's
blocking access to the r-utility ports (it's one of the first things we did
here:)
Cheers
Tony .
[EMAIL PROTECTED] _--_|\ [EMAIL PROTECTED]
UNIX Systems Officer / *\ [EMAIL PROTECTED]
Faculty of Science \_.--._/ [EMAIL PROTECTED]
Uni of Southern Queensland v Toowoomba Australia
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
