HP-UX Reference (11i v1 05/09) - 4 File Formats (vol 8)

p
prpwd(4) prpwd(4)
EXAMPLES
The following is an example of a typical protected password database file:
perry:u_name=perry:u_id#101:\
:u_pwd=aZXtu1kmSpEzm:\
:u_minchg#0:u_succhg#653793862:u_unsucchg#622581606:u_nullpw:\
:u_suclog#671996425:u_suctty=tty1:\
:u_unsuclog#660768767:u_unsuctty=tty1:\
:u_maxtries#3:chkent:
This protected password database file is for the user
perry. The user id for perry is 101. This value
must match the
/etc/passwd entry for this user. The account has a password and its encrypted form is
specified by the u_pwd field.
The database file specifies a minimum password change time of 0, indicating the password can be changed
at any time. Furthermore, the account is permitted to have a null password (
u_nullpw). The account has
a maximum consecutive unsuccessful login threshold of 3 attempts indicating that the account will be
locked after three failed attempts (
u_maxtries ). The remaining fields provide account information such
as the last successful and unsuccessful password change times as well as the last successful and unsuccess-
ful login times and terminal names.
AUTHOR
prpwd was developed by HP.
NOTES
The getprpwent(3) routines are used to parse the protected password database files into a structure that
can used by programs. A flag in the structure indicates whether a particular field in the structure and
hence the field is defined. System default values are also provided in the structure. These values are
derived from the /tcb/files/auth/system/default
field and can be used by programs in the
absence of a user specific value.
SEE ALSO
login(1), spell(1), users(1), acceptable_password(3), getprpwent(3), tod(3), gethostbyaddr(3N), authcap(4),
default(4),
HP-UX 11i Version 1: September 2005 3 Hewlett-Packard Company Section 4233