Man Pages (1M): Maintenance and Administration Commands

in.rshd(1M)

NAME

in.rshd, rshd- Remote shell server

SYNOPSIS

in.rshd

host.port

DESCRIPTION

in.rshd is the server for the rsh(1) program. The server provides remote execution facilities with authentication based on privileged port numbers.

in.rshd is invoked by inetd(1M) each time a shell service is requested, 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 host address (in hex) and port number (in decimal) are the arguments passed to in.rshd .
The server reads characters from the socket up to a null ( 0 ) byte. The resultant string is interpreted as an ASCII number, base 10.
If the number received in step 1 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 0-1023.
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 hosts(4) ), the server aborts the connection. Please refer to the SECURITY section below for more details.
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 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 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.
in.rshd checks whether logins are currently allowed by looking for an /etc/nologin file. If the file exists, the connection is terminated. If logins are allowed, the user is validated according to the following steps. The remote user name is looked up in the password file and a chdir is performed to the user's home directory. If the lookup fails, the connection is terminated. If the chdir fails, it does a chdir to / (root). If the user is not the superuser, (user ID 0), and if the pam_rhosts_auth PAM module is configured for authentication, the file /etc/hosts.equiv is consulted for a list of hosts considered "equivalent". If the client's host name is present in this file, the authentication is considered successful. See SECURITY below for a discussion of PAM authentication.

If the lookup fails, or the user is the superuser, then the file .rhosts in the home directory of the remote user is checked for the machine name and identity of the user on the client's machine. If this lookup fails, the connection is terminated
A null byte is returned on the connection associated with the stderr and the command line is passed to the normal login shell of the user. (The PATH variable is set to /usr/bin .) The shell inherits the network connections established by in.rshd .

SECURITY

in.rshd uses pam(3) for authentication, account management, and session management. The PAM configuration policy, listed through /etc/pam.conf , specifies the modules to be used for in.rshd . Here is a partial pam.conf file with entries for the rsh command using rhosts authentication, UNIX account management, and session management module.

rsh	auth	required	/usr/lib/security/pam_rhosts_auth.so.1
rsh	account	required	/usr/lib/security/pam_unix.so.1
rsh	session	required	/usr/lib/security/pam_unix.so.1

If there are no entries for the rsh service, then the entries for the "other" service will be used. To maintain the authentication requirement for in.rshd , the rsh entry must always be configured with the pam_rhosts_auth.so.1 module. Multiple authentication modules can not be listed for the rsh service.

SUMMARY OF TRUSTED SOLARIS CHANGES

If the /etc/nologin file exists, the server will not allow connections. The values of the trusted path, label view, and label-translation process attributes from the client process are propagated to the remote shell.

FILES

/etc/hosts.equiv

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWcsu

Trusted Solaris 7 Reference Manual

inetd(1M) , inetd.conf(4)

SunOS 5.7 Reference Manual

rsh(1) , hosts(4) , attributes(5)

DIAGNOSTICS

The following diagnostic messages are returned on the connection associated with stderr , after which any network connections are closed. An error is indicated by a leading byte with a value of 1 in step 9 above (0 is returned above upon successful completion of all the steps prior to the command execution).

locuser too long: The name of the user on the client's machine is longer than 16 characters.
remuser 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).
Hostname for your address unknown.: No entry in the host name database existed for the client's machine.
Login incorrect.: No password file entry for the user name existed.
Permission denied.: The authentication procedure described above failed.
Can't make pipe.: The pipe needed for the stderr was not created.
Try again.: A fork by the server failed.

NOTES

The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but it is useful in an "open" environment.

A facility to allow all data exchanges to be encrypted should be present.

Trusted Solaris 7 Last Revised 28 Oct 1996