This is a security requirement for Gecko updates in B2G: https://wiki.mozilla.org/B2G/Architecture/Runtime_Security#B2G_Update There are a number of requirements for this: 1. Build-time MAR verification enablement 2. Custom code and build changes for packaging and reading the signing cert(s). We can probably just package cert(s) directly in /system/b2g, but I'm open to alternatives (right now they are embedded into the updater.exe, but only for windows) 3. Define MOZ_VERIFY_MAR_SIGNATURE for the various talos configs in b2g/config/mozconfigs 4. Package update-settings.ini into /system/b2g (we will need some more clarification about the proper settings for this file)
This feels more like a tracking bug but we can at least start the client-side work here.
We will need the new B2G update channel IDs to update the various mozconfigs
Should we remove bug 799652 and bug 799655 from the depends-on list? I don't think we're going to do either of them soon.
We're marking this bug with the C1 milestone since it follows the criteria of "unfinished feature work" (see https://etherpad.mozilla.org/b2g-convergence-schedule). If this work is not finished by Nov19, this bug will need an exception and will be called out at the upcoming Exec Review.
Is this a meta-bug, or will any work actually happen in this bug?
Nothing to do here, it's just for tracking.
Thanks. Cleared blocking flag, and confirmed that the bugs that block this one are themselves blockers.
Technology we thought we needed, but until then it's an important tool in our technical tool box.
Resolving since we have support for this now, but we don't use it. No dependent bugs left.