Opened 3 years ago

Last modified 3 weeks ago

#19909 new task

Think about switching to Balrog for our server side Tor Browser update components

Reported by: gk Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by gk)

While discussing #19890 with Mozilla engineers we came across the topic on how we handle our server-side update part. It turns out that they basically did back then what we are doing now. They recommended to look at Balrog once we believe our needs do not scale anymore/or the system feels like being messed up etc. See: http://wiki.mozilla.org/Balrog for details.

Child Tickets

Change History (3)

comment:1 Changed 19 months ago by gk

Component: Applications/Tor bundles/installationApplications/Tor Browser

Moving to Tor Browser.

comment:2 Changed 3 months ago by gk

Description: modified (diff)

comment:3 Changed 3 weeks ago by gk

Balrog has capbability for throttling updates, which is interesting for moving to a regular release channel. Background: https://hearsum.ca/blog/streamlining-throttled-rollout-of-firefox-releases.html. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1246675.

Additionally, there might be ways to harden our update infrastructure against at least some attacks by having multiple sign-off requirements for update pushes. Background: https://hearsum.ca/blog/rings-of-power-multiple-signoff-in-balrog.html. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1278974.

Note: See TracTickets for help on using tickets.