Closed Bug 1162606 Opened 9 years ago Closed 7 years ago

Update add-on docs to cover AMO's automatic signing of extensions

Categories

(Developer Documentation Graveyard :: Add-ons, defect, P3)

Product:
Developer Documentation Graveyard
Component:
Add-ons
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sheppy, Assigned: wbamberg)

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: jorge@mozilla.com

:: Details

Starting in Firefox 40, extensions uploaded to AMO will automatically be signed. We need to update docs to explain this, and to tell developers not to try to self-sign their add-ons, since AMO will just re-sign them anyway.

Jorge recommends the following pages as information sources for this work:

http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/
https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/
https://wiki.mozilla.org/Addons/Extension_Signing

It's also important to note that this will only affect Firefox 40 and later and only extensions; other types of add-ons will not be auto-signed so the signing docs are still relevant for other applications and types of add-ons (like plugins, etc).
Assignee: nobody → wbamberg
I think this got done, https://developer.mozilla.org/en-US/Add-ons/Distribution
Please reopen, if I'm wrong.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.