« Adobe AIR Supports XSLT | Main | Privileged Modules: HOWTO validate signatures »

November 21, 2008

MAX2008: Maintain Security With Adobe AIR

That was the title of the session I did with Peleus Uhley on Wednesday. It's always fun to talk about security, especially with such an informed audience. Hopefully it was fun for them, too.

It's taken longer than I'd hoped but the slides are available here as PDF.

Or, just check them out below!

Posted by emalasky at November 21, 2008 6:43 PM

Comments

Hi Ethan,

I seem to have hit a brick wall with the security in AIR. I need to download and load in swf modules at runtime, but I want to keep them inside a network AND filesystem restricted sandbox, giving them access to methods via a parentSandboxBridge.

However it seems the normal method of loading modules only works for modules bundled at compile time, and the only way to load modules in at runtime from outside the AppDirectory is to allowLoadBytesCodeExecution which gives full access.

Is there any way I can get AIR to let me run downloaded modules in a sandbox?

Thanks

Rob

Posted by: RobMcM at February 5, 2009 10:13 AM

Flex 3.2 supports modules that are not imported into the loader's SecurityDomain. This means that an AIR app can load local untrusted modules from the filesystem without getting SecurityError exceptions.

Posted by: Ethan at February 5, 2009 10:27 AM

If I do this using the ModuleManager.getModule( file.url ) where file is an instance of the File class resolved to my Flex swf () I get the following error:

"SWF is not a loadable module"

There is an explanation here:

http://blogs.adobe.com/aharui/2007/03/swf_is_not_a_loadable_module.html

However as this is coming from a local file:// url I can't expose a cross domain policy file.

I also can't add sandboxe bridges, or security/app domains as it's not loaded using the Loader class.

Any more info would be really helpful, any reference to bridges is in HTML. Thanks

Posted by: RobMcM at February 6, 2009 5:05 AM

Flex 3.2 supports modules that are not imported into the loader's SecurityDomain. This means that an AIR app can load local untrusted modules from the filesystem without getting SecurityError exceptions.
http://www.tradestead.com

Posted by: a at February 11, 2009 1:08 AM

Post a comment




Remember Me?


Copyright © 2009 Adobe Systems Incorporated. All rights reserved.
Use of this website signifies your agreement to the Terms of Use and Online Privacy Policy (updated 07-14-2009).