Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

Table 44 Product Permissions
Permission to users to change and delete the product and/or product information.w (write)
Permission granted to target_hosts to read the source-depot product. (that is, grant permission
to a remote system to install the protected product).
r (read)
Permission to edit or change the ACL.c (control)
Permission to test access to an object.t (test)
A sample product ACL that grants user swadm and the creator of the product all permissions and
allows open read permission (allowing free distribution to all systems) would be:
user:swadm:crw
object_owner:crw
any_other:-r-
NOTE: When a product object is created, it is automatically protected by a default ACL from
the depot/root source or, absent that, one from the host.
ACL Templates
There are two ACLs that are used to create the initial ACLs that protect newly created objects:
product ACL templates (global_product_template or product_template) and container
ACL templates (global_soc_template).
Figure 56 ACL Templates
When a product is put into a depot with swcopy or swpackage, SD-UX uses a product ACL
template (provided by the depot that contains that product) to define the initial permissions of the
new product’s ACL.
SD-UX uses the product ACL template of the host system (global_product_template) to
initialize the product ACL template of the new depot and uses the container ACL template of the
host system (global_soc_template) to initialize depot and root ACLs.
Thus, there are three ACLs on the host:
• Host ACL
Attached to and controlling access to the host object itself.
• Container ACL Template (global_soc_template)
Used to initialize the ACL protecting new depots and roots created on the host.
• Product ACL Template (global_product_template)
The ACL that is used to initialize the product ACL template on depots that are created on the
host.
ACL Entries 155