1 .\" Copyright (c) 1983 Regents of the University of California.
2 .\" All rights reserved. The Berkeley software License Agreement
3 .\" specifies the terms and conditions for redistribution.
5 .\" @(#)rlogind.8c 6.3 (Berkeley) 5/24/86
7 .TH RLOGIND 8 "May 24, 1986"
10 rlogind, in.rlogind \- remote login server
12 .B "login stream tcp nowait root /usr/sbin/in.rlogind in.rlogind"
14 .B "tcpd login /usr/sbin/in.rlogind"
19 program. The server provides a remote login facility
20 with authentication based on privileged port numbers from trusted hosts.
23 listens for service requests at the port indicated in
24 the ``login'' service specification; see
26 When a service request is received the following protocol
29 The server checks the client's source port.
30 If the port is not in the range 0-1023, the server
31 aborts the connection.
33 The server checks the client's source address
34 and requests the corresponding host name (see
35 .BR gethostbyaddr (3),
39 If the hostname cannot be determined,
40 the dot-notation representation of the host address is used.
42 Once the source port and address have been checked,
44 allocates a pseudo terminal (see
46 and manipulates file descriptors so that the slave
47 half of the pseudo terminal becomes the
53 The login process is an instance of the
55 program, invoked with the
57 option. The login process then proceeds with the authentication
58 process as described in
60 but if automatic authentication fails, it reprompts the user
61 to login as one finds on a standard terminal line.
63 The parent of the login process manipulates the master side of
64 the pseduo terminal, operating as an intermediary
65 between the login process and the client instance of the
67 program. In normal operation, the packet protocol described
70 is invoked to provide ^S/^Q type facilities and propagate
71 interrupt signals to the remote programs. The login process
72 propagates the client terminal's baud rate and terminal type,
73 as found in the environment variable, ``TERM''; see
75 The screen or window size of the terminal is requested from the client,
76 and window size changes from the client are propagated to the pseudo terminal.
80 All diagnostic messages are returned on the connection
83 after which any network connections are closed.
84 An error is indicated by a leading byte with a value of 1.
94 The user's login shell could not be started.
96 The authentication procedure used here assumes the integrity
97 of each client machine and the connecting medium. This is
98 insecure, but is useful in an ``open'' environment.
100 A facility to allow all data exchanges to be encrypted should be
103 A more extensible protocol should be used.