In command, but has the disadvantage of not being as customizable and being able to connect only to Unix hosts.

rlogin is most commonly deployed on corporate or academic networks, where user account information is shared between all the unix machines on the network (often using Network Information Service). These deployments essentially trust most other machines (and the network infrastructure itself) and the rlogin protocol relies on this trust. rlogind allows logins without password (where rlogind trusts a remote rlogin client) if the remote host appears in the /etc/hosts.equiv file, or if the user in question has a .rhosts file in their home directory (which is frequently shared using Network File System).

rlogin has several serious security problems:

Due to these serious problems rlogin was rarely used across untrusted networks (like the public internet) and even in closed deployments it has fallen into relative disuse (with many Unix and Linux distributions no longer including it by default). Many networks which formerly relied on rlogin and telnet have replaced it with Secure shell and its rlogin-equivalent slogin.

The original Berkeley package which provides rlogin also features Rcp (remote-copy, allowing files to be copied over the network) and Rsh (remote-shell, allowing commands to be run on a remote machine without the user logging into it). These share the hosts.equiv and .rhosts access-control scheme (although they connect to a different daemon, rshd), and as such suffer from the same security problems. The ssh suite contains suitable replacements for both: scp replaces rcp, and ssh itself replaces both rlogin and rsh.

=External links=