This section tells you how to set up REX clients and REX servers.
It also explains how to configure added security for REX servers
and how to configure logging for the rexd
daemon.
To Configure REX Security |
 |
On each REX server, add the -r
option to the line in /etc/inetd.conf
that starts the rexd
daemon, as follows:
rpc stream tcp nowait root /usr/sbin/rpc.rexd 100017 1 \ rpc.rexd -r |
Issue the following command to force inetd
to reread /etc/inetd.conf:
Add lines to the /etc/hosts.equiv
file on the REX server to allow REX clients to use the server,
or
have each REX user add lines to a .rhosts
file in the user's home directory on the REX server to
allow access from REX clients.
The -r
option causes rexd
to deny requests from a user on a REX client unless the client is
listed in /etc/hosts.equiv
or the user's $HOME/.rhosts
file on the REX server.
A line in the /etc/hosts.equiv
or $HOME/.rhosts
file has the following syntax:
For example, if user paula
has accounts on REX clients broccoli
and cabbage and
on REX server cauliflower,
she would create a .rhosts
file in her home directory on cauliflower
with the following lines:
broccoli paula cabbage paula |
 |
 |  |
 |
 | CAUTION: The /etc/hosts.equiv
and $HOME/.rhosts
files create a significant security risk. Make sure these files
and users' home directories are writable only by the owner. |
 |
 |  |
 |
For more information, see the man pages for rexd(1M)
and hosts.equiv(4).
To Configure Logging for the rexd
Daemon |
 |
Use a text editor to add the -l log_file
option to the line in /etc/inetd.conf
that starts rexd,
as in the following example:
rpc stream tcp nowait root /usr/sbin/rpc.rexd 100017 1 \ rpc.rexd -l /var/adm/rexd.log |
Issue the following command to force inetd
to reread its configuration file:
When logging is turned on, rexd
logs any diagnostic, warning, and error messages to log_file.
If log_file
exists, rexd
appends messages to the file. If log_file
does not exist, rexd
creates it. Messages are not logged if the -l
option is not specified.
Information logged to the file includes date and time of the
error, host name, process ID and name of the function generating
the error, and the error message.
Different RPC services can share a single log file, because
enough information is included to uniquely identify each error.
Type man 1M rexd
for explanations of the messages logged by the rexd
daemon.
Many of the errors logged by rexd
are also returned to the user who issued the on
command. Type man 1 on
for explanations of the messages returned by the on
command.