Closed
Bug 1458324
Opened 6 years ago
Closed 6 years ago
Integrate MAR file signing with Autograph
Categories
(Release Engineering :: Release Automation: Signing, enhancement)
Release Engineering
Release Automation: Signing
Tracking
(firefox-esr60 fixed, firefox64 fixed)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: mozilla)
References
Details
(Whiteboard: [releng:q32018])
Attachments
(1 file)
As our first step of migrating signing backends, we will be migrating signing of updates to Autograph. This bug tracks the work required to update the signing workers to request signing from Autograph instead of from the signing servers.
Updated•6 years ago
|
Component: Release Automation: Other → Release Automation: Signing
Reporter | ||
Updated•6 years ago
|
Whiteboard: [releng:q22018] → [releng:q32018]
Comment 1•6 years ago
|
||
Basically just s/mar_sha384/autograph_mar384/g. repcakage_signing.py doesn't need a scope adjustment because it simply uses the format name to generate the scopes required.
Assignee | ||
Comment 2•6 years ago
|
||
Comment on attachment 9008572 [details]
Switch to autograph_mar384 signing.
Aki Sasaki [:aki] has approved the revision.
Attachment #9008572 -
Flags: review+
Pushed by bhearsum@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b970b71a9aa9 Switch to autograph_mar384 signing. r=aki
Comment 4•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b970b71a9aa9
Updated•6 years ago
|
Assignee: nobody → bhearsum
Comment 6•6 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-esr60/rev/52c5751575d9
status-firefox-esr60:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•