Overview Of Permission Controls - Adobe FLEX 2-PROGRAMMING ACTIONSCRIPT 3.0 Manual

Overview of permission controls

The Flash Player client run-time security model has been designed around resources, which
are objects such as SWF files, local data, and Internet URLs. Stakeholders are the parties who
own or use those resources. Stakeholders can exercise controls (security settings) over their
own resources, and each resource has four stakeholders. Flash Player strictly enforces a
hierarchy of authority for these controls, as the following illustration shows:
Administrator
(User Institution)
settings
User settings
Website settings
Author settings
Hierarchy of security controls
This means, for instance, that if an administrator restricts access to a resource, no other
stakeholders can override that restriction.
Administrator, user, and website controls are detailed in the following sections. Author
(developer) settings are described in the rest of this chapter.
Administrative user controls
An administrative user of a computer (a user who has logged in with administrative rights)
can apply Flash Player security settings that affect all users of the computer. In a nonenterprise
environment, such as on a home computer, there is usually one user who also has
administrative access. Even in an enterprise environment, individual users may have
administrative rights to the computer.
There are two types of administrative user controls:
The mms.cfg file
■
The Global Flash Player Trust directory
■
452 Flash Player Security