The
server
is the server for the
routine and, consequently, for the
program. The server provides remote execution facilities with
kerberos-based authentication or traditional pseudo-authentication
with privileged port numbers from trusted hosts.
The
server
listens for service requests at the port indicated in
the ``cmd'' service specification; see
When a service request is received
verifies the kerberos ticket supplied by the user.
For non-kerberised connections, the following protocol is initiated:
The server checks the client's source port.
If the port is not in the range 512-1023, the server
aborts the connection.
The server reads characters from the socket up
to a null (`\0') byte. The resultant string is
interpreted as an
number, base 10.
If the number received in step 2 is non-zero,
it is interpreted as the port number of a secondary
stream to be used for the
A second connection is then created to the specified
port on the client's machine. The source port of this
second connection is also in the range 512-1023.
The server checks the client's source address
and requests the corresponding host name (see
and
If the hostname cannot be determined,
the dot-notation representation of the host address is used.
The addresses for the hostname are requested,
verifying that the name and address correspond.
If address verification fails, the connection is aborted
with the message, ``Host address mismatch.''
A null terminated user name of at most 16 characters
is retrieved on the initial socket. This user name
is interpreted as the user identity on the
machine.
A null terminated user name of at most 16 characters
is retrieved on the initial socket. This user name
is interpreted as a user identity to use on the
machine.
A null terminated command to be passed to a
shell is retrieved on the initial socket. The length of
the command is limited by the upper bound on the size of
the system's argument list.
then validates the user using
which uses the file
and the
file found in the user's home directory. The
option prevents
from doing any validation based on the user's ``.rhosts'' file,
unless the user is the superuser.
If the file
exists and the user is not the superuser,
the connection is closed.
A null byte is returned on the initial socket
and the command line is passed to the normal login
shell of the user. The
shell inherits the network connections established
by
Transport-level keepalive messages are enabled unless the
option is present.
The use of keepalive messages allows sessions to be timed out
if the client crashes or becomes unreachable.
The
option causes all successful accesses to be logged to
as
messages.
Enable kerberos authentication.
Do not expect to be spawned by inetd and create a socket and listen on
it yourself.
Specifies the port number it should listen on in case the
flag has been given.
Vacuous, echo "Remote host requires Kerberos authentication" and exit.
Provides an encrypted communications channel. This option requires the
flag.
AFS only! Doesn't put the remote proccess in a new PAG.
DIAGNOSTICS
Except for the last one listed below,
all diagnostic messages
are returned on the initial socket,
after which any network connections are closed.
An error is indicated by a leading byte with a value of
1 (0 is returned in step 10 above upon successful completion
of all the steps prior to the execution of the login shell).
The name of the user on the client's machine is
longer than 16 characters.
The name of the user on the remote machine is
longer than 16 characters.
The command line passed exceeds the size of the argument
list (as configured into the system).
No password file entry for the user name existed.
The
command to the home directory failed.
The authentication procedure described above failed.
The pipe needed for the
wasn't created.
A
by the server failed.
The user's login shell could not be started. This message is returned
on the connection associated with the
and is not preceded by a flag byte.
SEE ALSO
BUGS
A more extensible protocol (such as Telnet) should be used.
