canmove, Confirmed users
1,570
edits
Firefox/Go Faster/Client Implementation Plan: Difference between revisions
Firefox/Go Faster/Client Implementation Plan (view source)
Revision as of 13:46, 23 July 2015
, 23 July 2015Improve notes about AMO's signing service
(Add note about maxVersion) |
(Improve notes about AMO's signing service) |
||
| Line 54: | Line 54: | ||
=Securing system add-ons= | =Securing system add-ons= | ||
System add-ons will need to be signed in a way that differentiates them from regular add-ons. This means either using a custom signing certificate or using the AMO signing service | System add-ons will need to be signed in a way that differentiates them from regular add-ons. This means either using a custom signing certificate or using the AMO signing service. AMO currently has two signing servers set up two sign preliminarily reviewed add-ons and fully reviewed add-ons. Clients can distinguish between the two based on a special string added to the Organizational Unit (OU) of the signing certificate for each add-on. Adding a third signing server that adds a new string to the OU is straightforward but AMO would need some updates to know to pass certain add-ons to that server. | ||
* '''Bug: Add-ons manager signature checks should enforce special rules for add-ons installed in the system add-ons location''' | * '''Bug: Add-ons manager signature checks should enforce special rules for add-ons installed in the system add-ons location''' | ||