Flash CS3 Documentation

Learning ActionScript 2.0 in Adobe Flash > Understanding Security > About local file security and Flash Player > Fixing legacy content deployed on local computers

Fixing legacy content deployed on local computers

If you published SWF files for Flash Player 7 or earlier that are deployed on local computers and communicate with the Internet, users must explicitly allow Internet communication. Users can stop content from breaking by adding the location of the SWF file on their local computer to the trusted sandbox in the Settings Manager.

To fix SWF files for local playback, use any of the following options:

Redeploy Run the Local Content Updater. The Local Content Updater reconfigures your SWF file to make it compatible with the security model (for Flash Player 8 and later). You reconfigure the local SWF file so it can either access only the network or only the local file system. For more information, and to download the Local Content Updater, see www.adobe.com/support/flashplayer/downloads.html.

Republish and redeploy  Republish the file with Flash. The authoring tool requires you to specify in the Publish Settings dialog box whether a local SWF file can access the network or the local file system--but not both. If you specify that a local SWF file can access the network, you also must enable permissions for that SWF file (and all local SWF files) in the SWF, HTML, data, and/or server files that it accesses. For more information, see Publishing files for local deployment.

Deploy new content  Use a configuration (.cfg) file in the #Security/FlashPlayerTrust folder. You can use this file to set network and local access permissions. For more information, see Creating configuration files for Flash development.

Flash CS3