All features are available in the Online Documentation.

Configuration under Windows NT, Windows 2000 or Windows XP:

configure -add remote_user local_user ip_list [-p password] adds a new user (being logged onto the remote machine as 'remote_user') to the trusted user database. This user will be impersonated as 'local_user' by passing 'password' to the WIN32 API. In addition, the remote IP address must match one in the 'ip_list'. Within the NT environment, no password will be required in the near future (Delegation).
Example: configure -add administrator \\MORDOR\administrator 123.23.4.*
will allow the administrator account on host 123.23.4.* to log on to this machine under the Domain MORDOR and the account administrator.

configure -list lists the trusted user database

configure -remove remote_user removes 'remove_user' from the trusted user database
 

Configuration under Windows 9X, Me:

• 131.234.92.*;getin;markus
  where getin is the remote user and markus is the local user.

Additional Information on the NT version:

• The executable rshd.exe contains fragments of a service. Calling rshd.exe without an option will not work since this method is used by the Service Manager of Windows NT, Windows 2000 or Windows XP. A user has to use options {-install, -remove, -d}
• dir is not a valid command but available with the preprocessor. extend your call to cmd /c dir in this case !
• Uninstalling will not remove the service but it's files. Removing the service requires to call rshd.exe -remove.

Examples:

• UNIX 2 NT: getin@flamenco [~] >>rsh pcpc11 -l \\\\pc2\\getin cmd /c dir c:\\   will retrieve the directory of c:\ being logged onto the domain PC2 as user getin. Please note the number of needed \ letters.

 
• An IP list may look like: (a * has to be the last entry when used)

          123.456.78.9
          123.456.78.*
          123.456.*
          123.456.7.8.9,123.456.7.8.0,123.456.*
 
• If you run the service in debug mode then (only needed for emergencies)
• set privileges for account (even administrative ones) which is doing the debugging and reboot
• 'Replace Token'
• 'Act as part of OS'
• reboot
• stop or remove the service
• call rshd -d

List of Fixed Bugs:

General:

• rsh.exe returns 0/1 upon failure/success

9X:

• Fixed compatibility call for using registry on 98 and 95. Yep, differences ... (07/08/1999)
• Added rsh.exe for 9X, better security (06/20/1999)
• Rshd on Windows 9X shuts down when user logs off has been fixed. A totally different mechanism had to be used. That way it took a little bit longer. Thanks for your patience.

NT:

• Added switch to allow or deny method of delegation (08/08/99)
• Fixed final trustbase bug, giving access denied on very short names
• Added command line extension up to 256 chars (V3, 06/20/1999)
• Added STDIN redirection. Please check out the id.exe example.
• Fixed configure -remove user call which messed up the trustbase
• Fixed encryption problem
• Fixed storing password
• some setup files were missing in the self extracting executable ... simple
• Users with administrative privileges are now allowed to install, remove, configure the service (was only allowed for Administrator account first)
• RSHD is checking on incoming IP correctly
• Problem with installation in directories which contain spaces in their names ...[user report] (fixed)
• Add user 'Everybody' in User Manager to be allowed to log on as batch !(fixed)
• * in IP List causes problems
• GetAccountSid problem solved (Allows user Everyone to Logon As Batch)
• stderr is piped back too

Known Problems:

• CryptoApi problems: On Windows NT 4.0 French OS, the crypto api causes problems due to Crypto Export restrictions. This is solved in W2K or later.
• POSIX executables can't be placed via rsh: commands like ls.exe, grep.exe which were build using NT's posix subsubsubsubsub-system can't be put in a security context and will fail to start up