Administering Secure RPC
In general, administering Secure RPC is accomplished as follows:
The following sections detail this procedure.
A domain name is chosen (for multiple domains,
more than one domain name is chosen).
Secure RPC domain names are set on participating machines,
and the SRPC_DOMAIN
tunable is set to the Secure RPC domain name
``Setting the Secure RPC domain name'').
For each user or host to be allowed access to Secure RPC services,
domain master machine administrators add entries
to their master /etc/publickey file.
keyserv and NIS daemons are started.
Administrators start keyserv, either manually or by means of a
The system administrators of client machines remove the comment character
that has commented out the keylogin command from their machine's
/etc/profile and they direct their Secure RPC users to add a trap
to their $HOME/.profile so that keylogout will be called
when their sessions end.
When slave servers are in use, master servers may have clients
as well as slaves.
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004