Objective-C Plugin Architecture Security (Mac, not iphone)

Posted by Tom Dalling on Stack Overflow See other posts from Stack Overflow or by Tom Dalling
Published on 2010-05-13T02:13:05Z Indexed on 2010/05/13 2:24 UTC
Read the original article Hit count: 377

Filed under:
|
|

I'm possibly writing a plugin system for a Cocoa application (Mac, not iphone).

A common approach is the make each plugin a bundle, then inject the bundle into the main application. I'm concerned with the security implications of doing this, as the bundle will have complete access to the Objective-C runtime. I am especially concerned with a plugin having access to the code that handles registration and serial keys.

Another plugin system we are considering is based on distributed notifications. Basically, each plugin will be a separate process, and they will communicate via distributed notifications only.

Is there a way to load bundles securely (e.g. sandboxing)? If not, do you see any problems with using distributed notifications? Are there any other plugin architectures that would be better?

© Stack Overflow or respective owner

Related posts about objective-c

Related posts about plugin