Manual page for RLOGIND(8C)
rlogind, in.rlogind - remote login server
is the server for the
program. The server provides a remote login facility
with authentication based on privileged port numbers.
is invoked by
when a remote login connection is established,
and executes the following protocol:
- The server checks the client's source port.
If the port is not in the range 0-1023, the server
aborts the connection. The client's address and port number
are passed as arguments to
in the form
with host in hex and port in decimal.
- 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
the server aborts the connection.
Once the source port and address have been checked,
allocates a pseudo-terminal (see
and manipulates file descriptors so that the slave
half of the pseudo-terminal becomes the
for a login process.
The login process is an instance of the
program, invoked with the
option. The login process then proceeds with the authentication
process as described in
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 pseudo-terminal, operating as an intermediary
between the login process and the client instance of the
program. In normal operation, the packet protocol described
is invoked to provide
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,
All diagnostic messages are returned on the connection
associated with the
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.
by the server failed.
- /usr/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
Created by unroff & hp-tools.
© by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97