Reland LZMA and SHA384 for 56 Beta 3

RESOLVED FIXED in Firefox 56

Status

()

Toolkit
Application Update
RESOLVED FIXED
11 months ago
10 months ago

People

(Reporter: rstrong, Assigned: rstrong)

Tracking

unspecified
mozilla56
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox56+ fixed, firefox57 unaffected)

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.
Summary: rELAND LZMA and SHA384 FOR 56 Beta 3 → Reland LZMA and SHA384 for 56 Beta 3
Tracking this for 56 since we intend on re-landing.
status-firefox56: --- → affected
tracking-firefox56: --- → +
Liz, when will it be ok to reland this for beta 3?
Flags: needinfo?(lhenry)
catlee, heads up regarding landing this for beta 3.
I checked with catlee and received the go ahead for this to land from him.
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)
Re-landed.
Assignee: nobody → robert.strong.bugs
Status: NEW → RESOLVED
Last Resolved: 10 months ago
status-firefox56: affected → fixed
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.