Extension Manager:Security Review: Difference between revisions

Extension Manager:Security Review (view source)

69 bytes added , 28 November 2007

canmove, Confirmed users

1,568

edits

@@ Line 187: / Line 187: @@
 '' Can the end user configure settings, via a UI or about:config? Hidden prefs? Environment variables?''
-The only relevant setting in the UI is that of the installation whitelist. All other settings are only visible in about:config and only really useful to developers.
+The only relevant setting in the UI is that of the installation whitelist. All other settings are only visible in about:config and only really useful to developers, particularly extensions.checkUpdateSecurity which can be used to allow installation of add-ons with insecure update paths.
 '' Are there build options for developers? [#ifdefs, ac_add_options, etc.]''
@@ Line 195: / Line 195: @@
 '' What ranges for the tunable are appropriate? How are they determined?''
-The only tunables are the intervals between checking for add-on updates and blocklist updates. Both of these default to a day, there is little point in them being any lower than this.
+No new tunables have been added since Firefox 2.
 '' What are its on-going maintenance requirements (e.g. Web links, perishable data files)?''
-None
+AMO have to maintain the release notes for add-ons for the new functionality to work.
 == Relationships to other projects - are there related projects in the community? ==