Simplify or automate signing of Jetpack XPIs
Please use "Edit with form" above to edit this page.
|Simplify signing XPIs in Jetpack|
|Release target||Jetpack Future|
|Status note||Investigating what signing of XPIs gets us.|
|Product manager||Dave Mason|
|Directly Responsible Individual||`|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
Currently, addon authors that want to sign their XPIs to self-host their extensions need to generate the XPI file, extract the install manifest, sign the manifest, put it back into the XPI, generate the hash of the XPI, add the hash to the update manifest, sign it, and then verify that everything works.
It would be nice if there was a way in the SDK to automate or simplify at least part of this process.
2. Users & use cases
Users who want to self-host their addons without paying for an SSL certificate to prove identity.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
The given value "
|761810||SecReview: Simplify signing XPIs in Jetpack||--||NEW|
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);" contains strip markers and therefore it cannot be parsed sufficiently.