Strengthening remote shell permissions (Windows)

After you have verified that the parallel engine configuration operates correctly, strengthen the remote shell (RSH) permissions.

Procedure

Modify the hosts.equiv file on the conductor node to narrow the range of trusted machines. Alternatively, set up an .rhosts file in the home account directory of each user.

Use the following syntax in the file:

Table 1. hosts.equiv and .rhosts syntax
Syntax	Meaning
+	All remote computers are to be trusted by the local computer.
+ `username`	`username` is to be trusted by the local computer. The plus sign and `username` are separated by whitespace in the file.
+ +	All remote users on all remote computers are to be trusted by the local computer. The plus signs are separated by whitespace in the file.

In all cases, the user ID that is specified by the remote user, either explicitly or implicitly, must have a valid account and a valid entry in the Windows LSA database on the local computer.

For example, user dstage issues the following command on remote computer exampleremote:

rsh -l dstage examplelocal ls

This command lists the contents of the dstage user home account on the local machine examplelocal if both of the following criteria are true:

Computer exampleremote is resolvable in the hosts.equiv file, or hosts.equiv contains two plus signs (+ +).
A valid entry exists for the local user dstage in the Windows LSA database on the local computer examplelocal.