Software Distributor Administration Guide (March 2009)

Table Of Contents
9 SD-UX Security
During the SD-UX installation, a default security setup is created. This chapter explains
basic SD-UX security, introduces the swacl command, presents examples of common
tasks, and provides in-depth discussion of how SD-UX manages security.
Table 9-1 Chapter Topics
Topic and Page
“Overview” (page 183)
“The swacl Command ” (page 184)
“Basic Security Tasks ” (page 187)
“How ACLs are Matched to the User ” (page 195)
ACL Entries ” (page 196)
“Security on SD-UX Systems ” (page 204)
“SD-UX Internal Authentication ” (page 206)
“RPC Authorization” (page 208)
“Security Use Models ” (page 210)
“Permission Requirements, by Command ” (page 213)
9.1 Overview
Along with the traditional HP-UX file access protection, SD-UX uses Access Control
Lists (ACLs) to authorize access to the primary objects on which it manages software:
Hosts
Roots (software installed on a host)
Depots
Products within depots
An ACL consists of a set of entries associated with an object when it is created.
9.1.1 Default Security
The following security scheme exists by default:
The local superuser always has access to all local objects.
Read access is provided to all users on the network who use the same SD-UX
shared secret via the any_other ACL.
9.1 Overview 183