1RLOGIND(8) BSD System Manager's Manual RLOGIND(8)
2
4 rlogind — remote login server
5
7 rlogind [-ahlLn]
8
10 Rlogind is the server for the rlogin(1) program. The server provides a
11 remote login facility with authentication based on privileged port num‐
12 bers from trusted hosts.
13 Options supported by rlogind:
15 -a Ask hostname for verification.
17 -h Permit use of superuser “.rhosts” files.
19 -l Prevent any authentication based on the user's “.rhosts” file. If
21 the user is logging in as the superuser and the -h option is
22 used, “.rhosts” processing is still enabled.
23 -L Prevent any authentication based on “.rhosts” or “hosts.equiv”
25 information.
26 -n Disable keep-alive messages.
28 The -h, -l, and -L flags are not used if PAM (Pluggable Authentication
30 Module) support is in use. In this case the same effects can be achieved
31 by editing /etc/pam.conf.
32 The -h and -l options should also not be trusted without verifying that
34 they work as expected with the particular version of libc installed on
35 your system (and should be tested again after any libc update) because
36 some versions of libc may not honor the internal flags used by rlogind.
37 As the -L option bypasses the libc functions entirely, it is not subject
38 to this problem.
39 Also note that the design of the .rhosts system is COMPLETELY INSECURE
41 except on a carefully firewalled private network. Always use the -L
42 option under all other circumstances. Also, since rlogind does not
43 encrypt communications, it should not, in general, be used at all. Con‐
44 sider ssh(8).
45 Rlogind listens for service requests at the port indicated in the
47 ``login'' service specification; see services(5). When a service request
48 is received the following protocol is initiated:
49 1. The server checks the client's source port. If the port is not in
51 the range 512-1023, the server aborts the connection.
52 2. The server checks the client's source address and requests the cor‐
54 responding host name (see gethostbyaddr(3), hosts(5) and named(8)).
55 If the hostname cannot be determined, the dot-notation representa‐
56 tion of the host address is used. If the hostname is in the same
57 domain as the server (according to the last two components of the
58 domain name), or if the -a option is given, the addresses for the
59 hostname are requested, verifying that the name and address corre‐
60 spond. Normal authentication is bypassed if the address verifica‐
61 tion fails.
62 Once the source port and address have been checked, rlogind proceeds with
64 the authentication process described in rshd(8). It then allocates a
65 pseudo terminal (see pty(4)), and manipulates file descriptors so that
66 the slave half of the pseudo terminal becomes the stdin, stdout, and
67 stderr for a login process. The login process is an instance of the
68 login(1) program, invoked with the -f option if authentication has suc‐
69 ceeded. If automatic authentication fails, the user is prompted to log
70 in as if on a standard terminal line.
71 The parent of the login process manipulates the master side of the pseudo
73 terminal, operating as an intermediary between the login process and the
74 client instance of the rlogin program. In normal operation, the packet
75 protocol described in pty(4) is invoked to provide ‘^S/^Q’ type facili‐
76 ties and propagate interrupt signals to the remote programs. The login
77 process propagates the client terminal's baud rate and terminal type, as
78 found in the environment variable, ‘TERM’; see environ(7). The screen or
79 window size of the terminal is requested from the client, and window size
80 changes from the client are propagated to the pseudo terminal.
81 Transport-level keepalive messages are enabled unless the -n option is
83 present. The use of keepalive messages allows sessions to be timed out
84 if the client crashes or becomes unreachable.
85
87 All initial diagnostic messages are indicated by a leading byte with a
88 value of 1, after which any network connections are closed. If there are
89 no errors before login is invoked, a null byte is returned as in indica‐
90 tion of success.
91 Try again.
93 A fork by the server failed.
94
96 login(1), ruserok(3), rshd(8)
97
99 The authentication procedure used here assumes the integrity of each
100 client machine and the connecting medium. This is insecure, but is use‐
101 ful in an ``open'' environment.
102 A facility to allow all data exchanges to be encrypted should be present.
104 A more extensible protocol should be used.
106
108 The rlogind command appeared in 4.2BSD.
109Linux NetKit (0.17) March 16, 1991 Linux NetKit (0.17)