BSD 4_2 development
[unix-history] / usr / man / man8 / rlogind.8c
CommitLineData
8d07919b
C
1.TH RLOGIND 8C "4 March 1983"
2.UC 4
3.SH NAME
4rlogind \- remote login server
5.SH SYNOPSIS
6.B /etc/rlogind
7[
8.B \-d
9]
10.SH DESCRIPTION
11.I Rlogind
12is the server for the
13.IR rlogin (1C)
14program. The server provides a remote login facility
15with authentication based on privileged port numbers.
16.PP
17.I Rlogind
18listens for service requests at the port indicated in
19the ``login'' service specification; see
20.IR services (5).
21When a service request is received the following protocol
22is initiated:
23.IP 1)
24The server checks the client's source port.
25If the port is not in the range 0-1023, the server
26aborts the connection.
27.IP 2)
28The server checks the client's source address.
29If the address is associated with a host for which no
30corresponding entry exists in the host name data base (see
31.IR hosts (5)),
32the server aborts the connection.
33.PP
34Once the source port and address have been checked,
35.I rlogind
36allocates a pseudo terminal (see
37.IR pty (4)),
38and manipulates file descriptors so that the slave
39half of the pseudo terminal becomes the
40.B stdin ,
41.B stdout ,
42and
43.B stderr
44for a login process.
45The login process is an instance of the
46.IR login (1)
47program, invoked with the
48.B \-r
49option. The login process then proceeds with the authentication
50process as described in
51.IR rshd (8C),
52but if automatic authentication fails, it reprompts the user
53to login as one finds on a standard terminal line.
54.PP
55The parent of the login process manipulates the master side of
56the pseduo terminal, operating as an intermediary
57between the login process and the client instance of the
58.I rlogin
59program. In normal operation, the packet protocol described
60in
61.IR pty (4)
62is invoked to provide ^S/^Q type facilities and propagate
63interrupt signals to the remote programs. The login process
64propagates the client terminal's baud rate and terminal type,
65as found in the environment variable, ``TERM''; see
66.IR environ (7).
67.SH DIAGNOSTICS
68All diagnostic messages are returned on the connection
69associated with the
70.BR stderr ,
71after which any network connections are closed.
72An error is indicated by a leading byte with a value of 1.
73.PP
74.B ``Hostname for your address unknown.''
75.br
76No entry in the host name database existed for
77the client's machine.
78.PP
79.B ``Try again.''
80.br
81A
82.I fork
83by the server failed.
84.PP
85.B ``/bin/sh: ...''
86.br
87The user's login shell could not be started.
88.SH BUGS
89The authentication procedure used here assumes the integrity
90of each client machine and the connecting medium. This is
91insecure, but is useful in an ``open'' environment.
92.PP
93A facility to allow all data exchanges to be encrypted should be
94present.