Administrator's Guide

• Last unsuccessful login time to the terminal
• Number of consecutive unsuccessful logins before terminal is locked
• Terminal lock flag
Only superusers can access these trusted system databases and can set the entries using
HP SMH. See devassign(4) and ttys(4).
A.3.7 Manipulating the Trusted System Databases
Use the library routines described in the following manpages to access information in
the password files and in other trusted system databases:
getdvagent(3) Manipulates device entries in /tcb/files/devassign
getprdfent(3) Manipulates system defaults in /tcb/files/auth/system/
default
getprpwent(3) Gets password entries from /tcb/files/auth/
getprtcent(3) Manipulates terminal control database, /tcb/files/ttys
getpwent(3C) Gets password entries from /etc/passwd
putpwent(3C) Writes password file entries to /etc/passwd
getspwent(3X) Gets password entries from /tcb/files/auth/ (provided for
backward compatibility)
putspwent(3X) Writes password entries to /tcb/files/auth/ (provided for
backward compatibility)
putprpwnam(3) Writes password file entries to /tcb/files/auth/
A.4 Guidelines for Trusted Backup and Recovery
Following are guidelines for backup and recovery on a trusted system:
• Use only fbackup and frecover to back up and recover files selectively. Only
fbackup and frecover retain access control lists (ACLs). Use the -A option of
these commands when backing up and recovering files for use on systems that do
not implement ACLs. For more information, see fbackup(1M) and frecover(1M).
• If you plan to recover the files to another system, be sure that the user's user name
and group name on both systems are consistent.
• Remember that the backup media is sensitive material. Allow access to the media
only on the basis of proven need.
• Label backup tapes and store them securely. Offsite storage provides maximum
security. Keep archives for a minimum of 6 months, then recycle the media.
• Use appropriate procedures to clean magnetic media to remove data before reuse.
• Perform daily incremental and full weekly backups.
Synchronize the backup schedule with the information flow in the organization. For
example, if a major database is updated every Friday, you might want to schedule
the weekly backup on Friday evenings.
A.4 Guidelines for Trusted Backup and Recovery 197