Copyright (c) 1983 Regents of the University of California.
All rights reserved. The Berkeley software License Agreement
specifies the terms and conditions for redistribution.

@(#)rlogind.8 6.1 (Berkeley) 04/27/85

C 5 rlogind - remote login server /etc/rlogind [ -d ] Rlogind is the server for the rlogin (1C) program. The server provides a remote login facility with authentication based on privileged port numbers.

Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services (5). When a service request is received the following protocol is initiated:

The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection. The server checks the client's source address. If the address is associated with a host for which no corresponding entry exists in the host name data base (see hosts (5)), the server aborts the connection.

Once the source port and address have been checked, rlogind allocates a pseudo terminal (see pty (4)), and manipulates file descriptors so that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance of the login (1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in rshd (8C), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line.

The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process and the client instance of the rlogin program. In normal operation, the packet protocol described in pty (4) is invoked to provide ^S/^Q type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as found in the environment variable, ``TERM''; see environ (7).

All diagnostic messages are returned on the connection associated with the stderr , after which any network connections are closed. An error is indicated by a leading byte with a value of 1.

``Hostname for your address unknown.''

No entry in the host name database existed for the client's machine.

``Try again.''

A fork by the server failed.

``/bin/sh: ...''

The user's login shell could not be started.

The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is useful in an ``open'' environment.

A facility to allow all data exchanges to be encrypted should be present.