so different vendors whip out "security" for different reasons. on mac, it is to prevent browser crashes, thus the separate process. on windows, it is all about preventing system corruption, thus protected mode -- which is especially funny, because you are limited in where you can WRITE a file but you can READ just about anything you want. so much for security.
by the way, we DO make very few assumptions about access. we use NSApp for flushing events & testing for stilldown and running a few select dialogs. that's about it. we are releasing the DreamFactory Player open source in the fall, i think that will be an important milestone. i think browser manufactures should focus on the voluntary aspect of plugin usage. our customers want to use dreamfactory to access cloud services. make it easy for them. i don't like the way some plugins can be used to "bomb" the users machine without notice. like the "dancing mortgage guy" on cnn. did you want to see him? best, bill On Tue, Jun 22, 2010 at 4:59 PM, Jens Alfke <j...@mooseyard.com> wrote: > > On Jun 22, 2010, at 4:47 PM, Bill Appleton wrote: > > > this IS sandboxed --- its in a separate process > > That’s not what “sandboxed” means. It refers to a process that’s running > with reduced privileges, i.e. it only gets to “play in the sandbox” without > having full access to the computer. For example, maybe it can only access > part of the filesystem, or can’t create windows, or can’t open network > sockets, or whatever. (OS X has a pretty complex set of privileges that can > be individually disabled for sandboxed processes.) > > I’m not sure what the eventual solution’s going to be for sandboxing > plugins, since some of them legitimately need such access. (Flash stores > cookies in your home directory, and some flash widgets can access webcams, > for instance.) But it’s probably a good idea to make as few assumptions as > possible about what environment you’re running in. > > The Chrome project is working on a new plugin API to eventually replace the > NPAPI; have you looked at it? > > —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
