4.1. AIR security4.1.1. Installation and updates4.1.1.1. AIR runtime installation location4.1.1.2. Seamless install (runtime and application)4.1.1.3. Manual install4.1.1.4. Application installation flow4.1.1.5. Application destination4.1.1.6. The AIR file system4.1.1.7. AIR application storage4.1.1.8. Updating Adobe AIR4.1.1.9. Updating AIR applications4.1.1.10. Uninstalling an AIR application4.1.1.11. Uninstalling Adobe AIR4.1.1.12. Windows registry settings for administrators4.1.2. Sandboxes4.1.2.1. About the AIR application sandboxes4.1.2.2. The application sandbox4.1.2.3. Privileges of content in non-application sandboxes4.1.2.3.1. Restrictions on loading CSS, frame, iframe, and img elements4.1.3. HTML security4.1.3.1. Overview on configuring your HTML-based application4.1.3.2. Code restrictions for content in different sandboxes4.1.3.2.1. Restrictions on using the JavaScript eval() method and similar techniques4.1.3.2.2. Restrictions on access to AIR APIs (for non-application sandboxes)4.1.3.2.3. Restrictions on calling the JavaScript Window.open() method4.1.3.2.4. Errors when calling restricted code4.1.4. Scripting between content in different domains4.1.4.1. About the AIR sandbox bridge4.1.4.2. Sandbox bridge example (SWF)4.1.4.3. Sandbox bridge example (HTML)4.1.4.4. Limiting API exposure4.1.5. Writing to disk4.1.6. Working securely with untrusted content4.1.6.1. Security.allowDomain()4.1.6.2. Scripting between application and non-application content4.1.6.3. Protection against dynamically generating unsafe SWF content4.1.7. Best security practices for developers4.1.7.1. Risk from importing files into the application security sandbox4.1.7.2. Risk from using an external source to determine paths4.1.7.3. Risk from using, storing, or transmitting insecure credentials4.1.7.4. Risk from a downgrade attack4.1.8. Code Signing4.2. Setting AIR application properties4.2.1. The application descriptor file structure4.2.2. Defining properties in the application descriptor file4.2.2.1. Defining the basic application information4.2.2.2. Defining the installation folder and program menu folder4.2.2.3. Defining the properties of the initial application window4.2.2.4. Specifying icon files4.2.2.5. Providing a custom user interface for application updates4.2.2.6. Allowing browser invocation of the application4.2.2.7. Declaring file type associations4.3. New functionality in Adobe AIR4.3.1. New runtime classes4.3.2. Runtime classes with new functionality4.3.3. New Flex components4.3.4. Service monitoring framework classes