search

adryantetsuo / google-opt-out-plugin

Automatically exported from code.google.com/p/google-opt-out-plugin
0 stars 0 forks source link

Let sign the Addon to fulfil Mozilla extension signing needs #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Requirement that Firefox add-ons (AMO and Non-AMO) be signed with 
mozilla-issued certificates to help get a handle on the proliferation of 
malicious and harmful add-ons, since Mozilla Firefox won't accept unsigned 
add-ons in future releases beginning with Firefox 41.

What version of the product are you using? On what operating system?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 
Firefox/39.0

google-opt-out-plugin 1.5

Please provide any additional information below.

https://wiki.mozilla.org/Addons/Extension_Signing
https://bugzilla.mozilla.org/show_bug.cgi?id=signed-addons
https://docs.google.com/document/d/1KhpDteoHFmVRkzlrT8v0N3F-KrPxLoZFM3mWmEmOses/
edit?pli=1

https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/
https://blog.mozilla.org/addons/2015/05/27/update-signing-new-developer-agreemen
t/

* How do I get my add-ons signed if they are hosted on AMO?
No action is required. We will automatically sign the latest reviewed versions 
of all add-ons currently hosted on AMO. You'll receive an email notification 
when this has been completed, and users will see that the add-on was updated. 
After the signature system goes live, all new versions will be signed 
automatically after they pass review.

* How do I get my add-ons signed if they are not hosted on AMO?
You will need to create an AMO account and submit your add-on. There will be an 
option where you indicate the add-on isn't hosted on AMO, and you'll be able to 
submit your add-on files without having them published on the site.

* How does the signing process work?
Files submitted for signing will go through an automated review process. If 
they pass this review, they are automatically signed and sent back to the 
developer. This process should normally take seconds. If the file doesn't pass 
review, the developer will have the option to request a manual review, which 
should take less than two days. This is not the same process that currently 
applies to AMO add-ons, which has been typically slower.

Addendum:

Same needs and procedure to be done for your
Google Analytics Opt-out Browser Add-on  
https://tools.google.com/dlpage/gaoptout?hl=en
https://support.google.com/analytics/answer/181881?hl=en

Original issue reported on code.google.com by sie...@gmail.com on 29 May 2015 at 10:17