keylogin(1)keylogin(1)NAMEkeylogin - decrypt and store secret key with keyserv
SYNOPSIS
[ ]
DESCRIPTION
The command prompts for a password, and uses it to decrypt the user's
secret key. The key may be found in the file (see publickey(4)), the
NIS map or entries in the LDAP directory in the user's home domain.
The sources and their lookup order are specified in the file (see nss‐
witch.conf(4)).
Once decrypted, the user's secret key is stored by the local key server
process, This stored key is used when issuing requests to any secure
RPC services, such as NFS. The program can be used to delete the key
stored by
will fail if it cannot get the caller's key, or the password given is
incorrect. For a new user or host, a new key can be added using
Options
Update the
file. This file holds the unencrypted secret key of the supe‐
ruser.
Only the superuser may use this option. It is used so that pro‐
cesses running as superuser can issue authenticated requests
without requiring that the administrator explicitly run as supe‐
ruser at system startup time (see keyserv(1M)).
The option should be used by the administrator when the host's
entry in the publickey database has changed, and the file has
become out-of-date with respect to the actual key pair stored in
the publickey database.
The permissions on the file are such that it may be read and
written by the superuser but by no other user on the system.
WARNINGS
HP-UX 11i Version 2 is the last HP-UX release on which NIS+ is sup‐
ported. LDAP is the recommended replacement for NIS+. HP fully sup‐
ports the industry standard naming services based on LDAP.
AUTHOR
was developed by Sun Microsystems, Inc.
FILES
Superuser's secret key
SEE ALSOchkey(1), keylogout(1), login(1), keyserv(1M), newkey(1M), pub‐
lickey(4), nsswitch.conf(4).
keylogin(1)