[sugar] [Sugar] Browse extension/plugin structure

[David Van Assche]

Well, we should try to keep the existing security in place and only
allow rpms to be installed (meaning the sugar team or olpc team would
have looked thoroughly through the source of the desired
extension/plugin.) Right now, the main reason this is happening is to
install google gears, which we desperately need to make offline Moodle
a reality. Making Browse installable via regular .xpi would probably
open up security holes, but since we are not doing that, I think
security should be allright. The email was really about what structure
to put in place for the components/extensions directories, as Browse
already (via XULrunner) allows for plugins. Or do you see it
differently?

Kind Regards,
David Van Assche

On Mon, Jul 14, 2008 at 11:48 PM, Michael Stone <michael at laptop.org> wrote:
> Please speak to me of your thoughts on the security implications of
> making Browse extensible.
>
> Thanks,
>
> Michael
>