One or two years ago I needed to connect Unix and Windows machine. Unix machine had to run a job on Windows and results delivered back to Unix . It is a quite simple task in Unix world but it can be little problem in the heterogenous network. Using some implementation of rsh daemon for Windows was the best way how to do it (for me of course). Because I couldn't find free and easy to use implementation, so it was the day when rshd spawned.
I am a Solaris administrator, but my mother tongue
is Pascal. That's the reason why I used Delphi for this task. Ancestors
rshd were C implementations for BSD Unix mixed up with rshd for Solaris
(I mean netgroups file, framework of connections rules in
.rhosts ...). I decided not to support Windows 95/98 because they are
not the right usable OSs for server applications. I started
programming on W2K Professional. Because W2K and NT containts many of
the same API functions I tried to use APIs which exists since
NT 4.0. I don't have access on Windows XP, but I assume backward
Because I started from Unix world the program HAD TO :) containts command line (eg for adding users to program by a batch,
starting, stopping, ...). Windows users on the contrary needs GUI. Result is a hybrid program which is started like console
application going to windows application and is it able to act as service.
When the application is started in GUI mode you can see the first screen. This is used for basic service setting. Here you can manipulate with the service eg. installing, uninstalling, starting and stopping service. If you need set or change other properties (change from automatic to manual start,...) of installed service please use Windows standard dialog for service setting.
This screen is used for the daemon settings how it will be manage incomming connections and some others. You'll see here which type of connection you want to accept, access logging , address lookup verification (it means that rshd will try find out IP address for remote computer name and translate back. Original and translated name have to be the same).
When the process on Unix try to change user identity and it has the rights to do it, OS trust it. On the contrary Windows need to known the new user password (if you want access and use network sources). Here you can see the table which holds the user names for remote connections and corresponding passwords (passwords are certainly ciphered). Every user on Windows has home directory. If this directory is on shared disk you can optionally put the connection entry. These entries will be used for mounting shared disk. If the user name is not local but you will use the account in the domain, you can put the whole name included the domain name.
You can enable or disable Rsh daemon monitoring. Simple telnet server is implemented for that reason. You can see who is connected from where, what is running which priority is set. Finally you can kill some or all connections or change processes priority.
Last screen is selfexplained "About". You just
ended the quick overview of rshd gui and service configuration. But
work is not ended now. Every user which wants to connect to Windows
MUST have in his home directory file .rhosts which describe who
and from the user can make the connections. Optionally you can use the
files netgroups and rhosts. This point is well known in the
Unix world and I wanted to do it as same as on Unix.
Because rsh connection protocol has been developed many years before in the times when networks were secure, rsh containts only
poor authentification mechanism. Today is better to use some solutions based on SSL and so on. But rsh daemons are still alive,
standard and they have the rock positions on Unix.
This program is now under Mozilla licence, but my
web has file size limitation and now I'm not able put source code here,
please write me and I'll send you source code via e-mail. Author gives
up any responsibility of misuse and financial or other detriments.
If you still want it, need it and love it, you can download the latest version of binary file here. Download size approx. 350kB.
Here is a beta version of rshd daemon, please give me info if you find a bug. Download size approx. 380kB.
6. Help me
If someone help me with revising of english part of documentation, I'll be really glad.
Mail to author:
Page created 9.Jan 2003, last updated 11.Apr 2006