rlogin prompt for password.

[nck2pg2]

B132L running 10.2

When I do
rlogin host_name -l root, It prompts me for password even the remote .rhosts file has my local machine_name. Please advise.

[U.SivaKumar_2]

hi,

do you have IP address and machine_name in the
host_name server's /etc/hosts file ?

regards,
U.SivaKumar

[nck2pg2]

Yes, all are there.

[Armin Feller]

Hi,

the problem is due to multiple interface cards on the source system. If you put in the correct name from the who -R command into the .rhosts file, you shouldn't have any more problems with the rlogin.

Best regrads,
Armin

[U.SivaKumar_2]

Hi,

Any error in /var/adm/syslog/syslog.log ?
Check the permissions of .rhosts
regards,
U.SivaKumar

[U.SivaKumar_2]

Also check /etc/inetd.conf for rlogind line.
Ensure that rlogind is not run with -l option in that file.

regards,
U.SivaKumar

[Jean-Louis Phelix]

hi,

If you want to rlogin from A to B then check :

- on A
nslookup B -> should give IP_of_B
nslookup IP_of_B -> should give B

- on B
same but with A instead of B

Everything should match.

Regards.

[Frank Slootweg]

What is the user who gives the rlogin command (probably not root)? That user name should also be in the .rhosts file, i.e.

from_host from_user

Please give us the (relevant)contents of the host_name:~root/.rhosts file and the ll(1) output for that file.

Before experimenting with rlogin, first experiment with the simpler remsh(1) command, i.e.

remsh hostname -l root date

[Pete Randall]

Unless you're root when you issue the rlogin command, this is normal and expected behaviour. In other words, a normal user should not be able to become root simply by issuing a rlogin command.

Pete

[Shannon Petry]

The file /etc/hosts.equiv is like a global .rhosts file, valid for any user except for root.

On secure sites, dont think of using either. On sites that can be insecure, I prefer to use /etc/hosts.equiv.

Make sure to list all hosts that need access, and that all hostnames can be listed in the file. If you are unsure, put both the hostname and IP address into the file.
$HOME/.rhosts can also be used, and is required for root access. Same rules apply for hostname resolution and/or adding IP's and hostnames to the file.

NOTE: roots $HOME by default is /, thus most users reference /.rhosts for root access. On systems where root's $HOME is not /, this will not work. I.E. my root home in Linux is /root. I must have a /root/.rhosts to enable root access without a password, /.rhosts is ignored.

Regards,
Shannon

[Steven E. Protter]

.rhosts files can be overridden by inetd.sec files.

That will stop password free login if not allowing the right hosts.

Take a look. If this is even a 10.20 feature and you have it.

[Oleg Zieaev_1]

Hello.

First, you might want to check /etc/inetd.conf line for login should not have -l at the end.
Second, /var/adm/inetd.sec file - check for exclusive deny of service for you host/user.

I would also check .rshost file to correspond hostnames in /etc/hosts or match output of nslookup.

Hope this helps,
0leg

[nck2pg2]

I found out that trusted system won't allow rlogin without prompting for password. Am I right?

[nck2pg2]

I found out that trusted system won't allow rlogin without prompting for password. Am I right?