NAME

in.rshd, rshd - Remote shell server

SYNOPSIS

in.rshd host. port

AVAILABILITY

SUNWcsu

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(1MTSOL) each time a shell service is requested, and executes the following protocol:

1)

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.

2)

The server reads characters from the socket up to a null (\0) byte. The resultant string is interpreted as an ASCII number, base 10.

3)

If it is not zero, the number received in Step 1 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.

4)

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.

5)

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.

6)

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.

7)

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.

8)

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, the process does a chdir to root (/). If the user is not the super-user, (user ID 0), 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. If the lookup fails, or if the user is the super-user, 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.

9)

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. The values of the trusted path, label view, and label-translation process attributes from the client process are propagated to the shell by in.rshd.

SUMMARY OF TRUSTED

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.

SOLARIS CHANGES

FILES

/etc/hosts.equiv

SEE ALSO

rsh(1), inetd(1MTSOL), inetd.conf(4TSOL), hosts(4)

DIAGNOSTICS

The following diagnostic messages are returned on the connection associated with stderr; then any network connections are closed. An error is indicated by a leading byte with a value of 1 in Step 9. (0 is returned 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 earlier 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 assumption is insecure but is useful in an "open" environment.

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