MACROMEDIA FLASH 8-LEARNING ACTIONSCRIPT 2.0 IN FLASH, Manual

Page: 692 / 830

692 Understanding Security
If you create applications that install on an end user’s hard disk, you might need to create a
configuration file in FlashPlayerTrust to specify a trusted directory for your application. You
can create configuration files inside the FlashPlayerTrust directory that specify the location of
the trusted application. See the pervious procedure for information on this directory and
creating configuration files.
You should develop a unique naming scheme to avoid conflicts with other applications that
might install files in this directory. For example, you might want to use your unique company
and software name in the filename to avoid conflicts.
For more information on configuration files, see www.macromedia.com/go/flashauthorcfg .
You can also create a unique configuration file to trust one or more directories. For detailed
information on security, see
www.macromedia.com/devnet/security/ and
www.macromedia.com/software/flashplayer/security/ .
About the sandboxType property
Flash Player 8’s
System.security.sandboxType
property returns the type of security
sandbox in which the calling SWF file is operating.
The
sandboxType
property has one of the four following values:
remote
The SWF file is hosted on the Internet and operates under domain-based
sandbox rules.
localTrusted The SWF file is a local file that has been trusted by the user, using either the
Global Security Settings Manager or a FlashPlayerTrust configuration file. The SWF file can
both read from local data sources and communicate with the network (such as the Internet).
localWithFile
The SWF file is a local file that has not been trusted by the user, and was not
published with a networking designation. The SWF file can read from local data sources but
cannot communicate with the network (such as the Internet).
NO
T
E
An installer is run by a user with administrative permission on a computer.
TI
P
If you do not want to use configuration files, you could publish your Flash applications to
a separate, testing server instead of providing clients or other developers SWF files to
run on their local hard disks.