Open Bug 1813699 Opened 3 years ago Updated 1 year ago

Android V3 signatures for Fenix

Categories

(Release Engineering :: Release Automation, enhancement)

All
Android
enhancement

Tracking

(Not tracked)

People

(Reporter: boek, Unassigned)

References

Details

From github: https://github.com/mozilla-mobile/fenix/issues/22448.

v3 signatures enable us to rotate signing key in case the private key leaked

Our CSO thinks we should tackle this now.

https://jira.mozilla.com/browse/FFXP-431

Do we also want this for focus-android?

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

From RELENG-718:

Once signingscript has added support for v3 signing formats, we need to enable it on various products by changing the format they’re signing with. This will need to be done for at least: Fenix, Focus/Klar, Reference Browser, and MozillaVPN. (There may be others, but these are the ones I came up with so far.)

Each of these defines the format in a slightly different place. Here’s where they were when I wrote this up:

For the browsers with multiple release channels, we should start with Nightly, and then adjust the other channels once we’re sure things are good there.

We should also coordinate with either engineers or QA when landing this, to make sure it gets tested on multiple device versions. See https://mozilla-hub.atlassian.net/browse/QA-1193 for initial testing done for this project.

Type: defect → enhancement
Component: General → Release Automation: Signing
Product: Fenix → Release Engineering

We'll get v3 signatures enabled on the Autograph side of things in bug 1842229.

Depends on: 1842229
Component: Release Automation: Signing → Release Automation
You need to log in before you can comment on or make changes to this bug.