Administering Secure RPC

In general, administering Secure RPC is accomplished as follows:

1. A domain name is chosen (for multiple domains, more than one domain name is chosen). Secure RPC domain names are set on participating machines, using the domainname(1Mnis) command, and the SRPC_DOMAIN tunable is set to the Secure RPC domain name (see ``Setting the Secure RPC domain name'').

2. 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.

3. keyserv and NIS daemons are started.

4. Administrators start keyserv, either manually or by means of a boot-time script.

5. 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.