(As far as I know) a sandbox for plugins is being worked on, but it is not enabled right now. There is a command line switch if you want to test it, though. --safe-plugins
☆PhistucK On Mon, Dec 14, 2009 at 03:37, Jean-Lou Dupont <jeanlou.dup...@gmail.com>wrote: > > > ... isn't there a sandbox (chroot ?) in place for NPAPI plugins too? > > > > No, they aren't sandboxed. They have the full privs of the current user. > > > > - a > > This means that the "EXECUTE" property of the file wasn't conserved. > I guess I could have change the file properties to make this work. > I should have investigated this issue before concluding prematurely > that a "sandbox" was at work. > > Thanks guys! > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
