Re: r* commands don't work

On Fri, 27 Feb 1998, Tim Sailer wrote: Part of the security behind the .rhosts files are that they will not work unless they are mode 644. This way only the owner can add to them. Make sure the ownership is correct too. I didn't know that, but it turns out that they were 644 (default umask

r* commands don't work

Hi, I sent a message about this when I had the problem at my last job. I left the job before ever resolving this. I'm at a new job now and I'm trying to integrate linux somehow into our environment. I plan on using linux for some minor development at first, just to get some linux machines in

AW: r* commands don't work

Richard G. Roberto asked: [...] However, I still can't get the r* commands to work. [...] I opened up .rhosts for root, hosts.equiv for everyone else, and even .rhosts for myself, but to no avail. [...] Let's review your setup. You want to be able to rsh/rlogin to root on a remote system,

Re: AW: r* commands don't work

On Fri, 27 Feb 1998 [EMAIL PROTECTED] wrote: Richard G. Roberto asked: [...] However, I still can't get the r* commands to work. [...] I opened up .rhosts for root, hosts.equiv for everyone else, and even .rhosts for myself, but to no avail. [...] Let's review your setup. You want

AW: AW: r* commands don't work

Hello Richard, you wrote: [...] - enable .rhosts for the superuser by adding -h to the in.rlogind optionlist in /etc/inetd.conf (man 8 rlogind)? on my system: [no -h in man 8 rlogind. Hmmm...] I have netstd 2.05-1 and netbase 2.04-1 with libc5 5.4.20-1. This might be part of the

Re: r* commands don't work

Richard G. Roberto wrote: I opened up .rhosts for root, hosts.equiv for everyone else, and even .rhosts for myself, but to no avail. I have no hosts.allow or hosts.deny file, nor am I using tcpd at all. Host names resolve via DNS or /etc/hosts with no problem. I tried having the hostname