Comments on: The about:sumo experiment http://blog.mozilla.com/sumo/2009/04/21/the-aboutsumo-experiment/ The support.mozilla.org (SUMO) project Tue, 07 Feb 2012 08:20:15 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Chris Ilias http://blog.mozilla.com/sumo/2009/04/21/the-aboutsumo-experiment/comment-page-1/#comment-22051 Chris Ilias Mon, 11 May 2009 19:07:40 +0000 http://blog.mozilla.com/sumo/?p=558#comment-22051 <b>Pseudonymous Coward</b>: Your comment seems to be about AMO and this blog is about support.mozilla.com (SUMO) not AMO. Try posting in the <a href="http://www.mozilla.org/community/developer-forums.html#general-development" rel="nofollow">mozilla.dev.amo newsgroup/mailing list</a>. Pseudonymous Coward: Your comment seems to be about AMO and this blog is about support.mozilla.com (SUMO) not AMO. Try posting in the mozilla.dev.amo newsgroup/mailing list.

]]> By: Pseudonymous Coward http://blog.mozilla.com/sumo/2009/04/21/the-aboutsumo-experiment/comment-page-1/#comment-21697 Pseudonymous Coward Sat, 02 May 2009 15:56:03 +0000 http://blog.mozilla.com/sumo/?p=558#comment-21697 Just recently, the NoScript/Adblock Plus controversy serves to highlight some fundamental problems with the questionable security model of the Firefox add-ons mechanism. Why are add-ons able to mess around with each other? Why must I trust that my Firefox browser will do the right thing now? An AMO policy is all well and good, but it is only as strong as its weakest adherent. What Mozilla needs to do is technologically enforce its AMO policy. Suggestions: 1. A strong Javascript sandbox. (A built-in NoScript, if you will.) 2. Why on earth do add-ons have such raw power in Firefox? We need a strong add-ons sandbox too. Seriously, Google Chrome at least has a very strong security model. That is far more important to establish before an add-ons mechanism, I think. If Mozilla can spend a significant amount of time competing with other browsers to copy the idea of Javascript JIT compilation, I think it should spend its time copying other virtues such as a rock-solid sandbox. Thank you. Just recently, the NoScript/Adblock Plus controversy serves to highlight some fundamental problems with the questionable security model of the Firefox add-ons mechanism. Why are add-ons able to mess around with each other? Why must I trust that my Firefox browser will do the right thing now?

An AMO policy is all well and good, but it is only as strong as its weakest adherent. What Mozilla needs to do is technologically enforce its AMO policy. Suggestions:

1. A strong Javascript sandbox. (A built-in NoScript, if you will.)
2. Why on earth do add-ons have such raw power in Firefox? We need a strong add-ons sandbox too.

Seriously, Google Chrome at least has a very strong security model. That is far more important to establish before an add-ons mechanism, I think. If Mozilla can spend a significant amount of time competing with other browsers to copy the idea of Javascript JIT compilation, I think it should spend its time copying other virtues such as a rock-solid sandbox.

Thank you.

]]> By: Bubo http://blog.mozilla.com/sumo/2009/04/21/the-aboutsumo-experiment/comment-page-1/#comment-21272 Bubo Sun, 26 Apr 2009 06:00:46 +0000 http://blog.mozilla.com/sumo/?p=558#comment-21272 Do i get to proof read? Do i get to proof read?

]]>