Administrator's Guide

PRIV_CORESYSATTR and PRIV_HOSTATTR. The PRIV_MOUNT privilege is divided
into PRIV_FSMOUNT and PRIV_SWAPCTL. The PRIV_DEVOPS privilege is divided into
PRIV_RDEVOPS and PRIV_PTYOPS.
This new privilege model allows applications, when explicitly developed to be aware of
HP-UX privileges (see privileges(5)), to have finer control over the administrative
capabilities that were controlled by the PRIV_SYSATTR, PRIV_MOUNT and
PRIV_DEVOPS privileges.
System calls that manage a system's host and domain names (see setdomainname(2),
sethostname(2), and setuname(2)) now require the PRIV_HOSTATTR privilege.
System calls that manage a system's swap space (see swapctl(2) and swapon(2)) now
require the PRIV_SWAPCTL privilege.
System calls that manage streams-based terminals (see ldterm(7)) now require the
PRIV_PTYOPS privilege.
The above system calls will return -1 with errno set to either EPERM or EACCESS if the
required privilege is not possessed by the calling process.
To maintain backward compatibility for HP-UX privileges aware applications in the new
privilege model, the string representation of the PRIV_SYSATTR, PRIV_DEVOPS, and
PRIV_MOUNT privileges will continue to be supported as compound privileges
[PRIV_CORESYSATTR and PRIV_HOSTATTR], [PRIV_RDEVOPS and PRIV_PTYOPS],
and [PRIV_SWAPCTL and PRIV_FSMOUNT] in the user space. All HP-UX core kernel
modules and commands have been updated to support the new privileges. This ensures
standard and typical HP-UX privileges aware applications to continue to work in the new
privilege model without requiring any changes unless you want to take advantage of the
new privilege model to gain finer control.
7.4 Configuring Applications with Fine-Grained Privileges
Applications that are written or modified to support fine-grained privileges are called
privilege-aware applications. You must register privilege-aware applications using the
setfilexsec command. Once registered, the security attributes associated with a
binary file are stored in a configuration file and maintain persistence across reboot. This
is normally done for you when you install and configure privilege-aware applications
using the SD-UX utilities.
Older HP-UX applications, or legacy applications, are not privilege-aware. You can
configure legacy applications that run with UID=0 to run with fine-grained privileges.
To configure legacy applications using HP-UX RBAC, see Section 8.5.4.
136 Fine-Grained Privileges