HP-UX System Administrator's Guide: Security Management HP-UX 11i v3 (B3921-90020, September 2010)

Table Of Contents
Table 5-5 HFS and JFS ACL Equivalents (continued)
JFS EquivalentHFS Name
—none—setaclentry(3C)
—none—strtoacl(3C)
aclsort(3C)—none—
aclv(5)acl(5)
5.6 ACLs and NFS
The Network File System (NFS) has no facility to pass ACL information about remote
files. Therefore, ACLs are not visible on remote files by NFS. The ls -l command
will not show that ACLs exist on a remote file, but the ACL control over access
permissions remains effective.
Individual manpage entries specify the behavior of the various system calls, library
calls, and commands under these circumstances.
IMPORTANT: Use caution when transferring a file with optional entries over a network,
or when manipulating a remote file, because NFS can delete optional entries with no
notification.
5.7 Security Considerations for /dev Device Special Files
Access to all devices in the system is controlled by device special files, which enable
programs to be device independent. These files are shipped with permission settings
that enable proper use and maximum security.
If you install any other device special files, see insf(1M) for information about correct
permission settings.
Because device special files can be as vulnerable to tampering as any other file, observe
the following precautions:
Keep all device special files in the /dev directory.
Protect the memory files, /dev/mem and /dev/kmem, from casual access, because
these files contain sensitive user information. For example, a program that watches
memory for an invocation of the login program might copy the password from
the login program buffers when a user types it in. The file protections should be
set to:
crw-r----- 1 bin sys 3 0x000001 Jun 9 2006 /dev/kmem
crw-r----- 1 bin sys 3 0x000000 Jun 9 2006 /dev/mem
Protect all disk special files:
5.6 ACLs and NFS 103