Интерактивная система просмотра системных руководств (man-ов)
rshd (8)
>> rshd (8) ( FreeBSD man: Команды системного администрирования )
rshd (8) ( Linux man: Команды системного администрирования )
BSD mandoc
NAME
rshd
- remote shell server
SYNOPSIS
[-aDLln
]
DESCRIPTION
The
utility
is the server for the
rcmd(3)
routine and, consequently, for the
rsh(1)
utility.
The server provides remote execution facilities
with authentication based on privileged port numbers from trusted hosts.
The
utility listens for service requests at the port indicated in
the
``cmd''
service specification; see
services(5).
When a service request is received 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
NUL
(`\0') byte.
The resultant string is
interpreted as an
ASCII
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
stderr
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
gethostbyaddr(3),
hosts(5)
and
named(8)).
If the hostname cannot be determined or the hostname and address do
not match after verification,
the dot-notation representation of the host address is used.
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
client 's
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
server 's
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.
The
utility then validates the user using
ruserok(3),
which uses the file
/etc/hosts.equiv
and the
.rhosts
file found in the user's home directory.
The
-l
option prevents
ruserok(3)
from doing any validation based on the user's
.rhosts
file,
unless the user is the superuser.
A
NUL
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
.
The options are as follows:
-a
This flag is ignored, and is present for compatability purposes.
-D
Sets the TCP_NODELAY socket option, which improves the performance
of small back-to-back writes at the expense of additional network
traffic.
-L
Causes all successful accesses to be logged to
syslogd(8)
as
auth.info
messages.
-l
Do not use the user's
.rhosts
file for authentication, unless the user is the superuser.
-n
Turn off transport level keepalive messages.
This will prevent sessions
from timing out if the client crashes or becomes unreachable.
FILES
/etc/hosts
/etc/hosts.equiv
/etc/login.conf
$HOME /.rhosts
/etc/pam.conf
uses
/etc/pam.conf
entries with service name
``rsh''
Authentication modules requiring passwords (such as
pam_unix
are not supported.
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).
Locuser too long.
The name of the user on the client's machine is
longer than 16 characters.
Ruser too long.
The name of the user on the remote machine is
longer than 16 characters.
Command too long.
The command line passed exceeds the size of the argument
list (as configured into the system).
Login incorrect.
No password file entry for the user name existed
or the authentication procedure described above failed.
Remote directory.
The
chdir(2)
function to the home directory failed.
Logins not available right now.
The
rsh(1)
utility was attempted outside the allowed hours defined in
/etc/login.conf
for the local user's login class.
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
present.
Post-PAM,
Fx also needs the following patch applied besides properly configuring
.rhosts
