| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Berkeley Remote Login (rlogin) (Page 2 of 2) Automating rlogin In some organizations, many different UNIX hosts are used every day and needing to type passwords all the time when using rlogin was deemed to be somewhat of a chore. On these systems, it is possible for administrators to set up control files that specify combinations of host names, user names and passwords. If set up correctly, this enables an authorized user to utilize rlogin to remotely access a host automatically, without having to enter either a login name or password, which can be a time savings. As originally designed, rlogin is a classic example of a protocol from the early days of TCP/IP: it emphasizes simplicity and usability over security. This is especially true of the automated login process just described. The original schemes used by rlogin for authentication are considered inadequate for modern TCP/IP internetworks, especially those connected to the Internet. Later versions of rlogin have been enhanced with more secure authorization methods. There is also a newer program called slogin (for secure login) that uses stronger authentication and encryption, and is intended to replace rlogin on newer systems.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||