Closed
Bug 1387238
Opened 7 years ago
Closed 7 years ago
Reland LZMA and SHA384 for 56 Beta 3
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | + | fixed |
firefox57 | --- | unaffected |
People
(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)
References
Details
Bug 1387231 will backout the LZMA and SHA384 changes on 56 Beta. They should be relanded on 56 Beta for Beta 3. Specifically, the following from bug 641212. Pushed by rstrong@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/89a4dd1ba384 use lzma compression for application update. Part 1 - xz-embedded build config changes. r=glandium, a=app_update_lzma https://hg.mozilla.org/mozilla-central/rev/692137868c6b use lzma compression for application update. Part 2 - add xe-embedded decompression support to the updater. r=mhowell, , a=app_update_lzma https://hg.mozilla.org/mozilla-central/rev/8fbee1d5b748 use lzma compression for application update. Part 3 - test changes to support the new test mar file size and additional logging. r=mhowell, a=app_update_lzma https://hg.mozilla.org/mozilla-central/rev/620ff920d666 use lzma compression for application update. Part 4 - app update test mar files created using lzma compression. r=mhowell, a=app_update_lzma and the following from bug 1105689 Pushed by rstrong@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/f72832cc0480 use SHA384 certificates to sign app update mar files. Part 1 - convert the libmar code from SHA1 to SHA384. r=mhowell, r=spohl, a=app_update_sha384 https://hg.mozilla.org/mozilla-central/rev/a0469afc3098 use SHA384 certificates to sign app update mar files. Part 2 - libmar test mar files signed with a SHA384 cert. r=mhowell, a=app_update_sha384 https://hg.mozilla.org/mozilla-central/rev/0fcbe72581bc use SHA384 certificates to sign app update mar files. Part 3 - libmar test extracted SHA384 signatures from the test mar files. r=mhowell, a=app_update_sha384 https://hg.mozilla.org/mozilla-central/rev/92f6879a8f9f use SHA384 certificates to sign app update mar files. Part 4 - app update SHA384 DER encoded certtificates. r=mhowell, a=app_update_sha384 https://hg.mozilla.org/mozilla-central/rev/23d91b010a0e use SHA384 certificates to sign app update mar files. Part 5 - app update test change for the new test mar file size. r=mhowell, a=app_update_sha384 https://hg.mozilla.org/mozilla-central/rev/a6c502679d44 use SHA384 certificates to sign app update mar files. Part 6 - app update test mar files signed with a SHA384 certificate. r=mhowell, a=app_update_sha384 The mar generation scripts that were backed out in Bug 1387231 should not be relanded until after the 56 Beta 3 mar files have been generated.
Assignee | ||
Updated•7 years ago
|
Summary: rELAND LZMA and SHA384 FOR 56 Beta 3 → Reland LZMA and SHA384 for 56 Beta 3
Comment 1•7 years ago
|
||
Tracking this for 56 since we intend on re-landing.
status-firefox56:
--- → affected
tracking-firefox56:
--- → +
Assignee | ||
Comment 2•7 years ago
|
||
Liz, when will it be ok to reland this for beta 3?
Flags: needinfo?(lhenry)
Assignee | ||
Comment 3•7 years ago
|
||
catlee, heads up regarding landing this for beta 3.
Assignee | ||
Comment 4•7 years ago
|
||
I checked with catlee and received the go ahead for this to land from him.
Comment 5•7 years ago
|
||
OK, that's fine, we can track it in this bug I guess. Since there is no patch to approve here... Ryan can you go ahead and re-land the patch in bug 1387231 on beta? Thanks.
Flags: needinfo?(lhenry) → needinfo?(ryanvm)
Comment 6•7 years ago
|
||
Re-landed.
Assignee: nobody → robert.strong.bugs
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → unaffected
Flags: needinfo?(ryanvm)
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•