Consider using balrog everywhere

[bakulf]

Right now we have 2 ways to keep track of client updates: the REST API (endpoint: https://vpn.mozilla.org/api/v1/vpn/versions) and Balrog. So far we use balrog only for Windows and MacOS.

What I propose here is to use balrog even on Linux, IOS, and Android. Here is a list of reasons:

• it's not good to have 2 ways to update clients. They can go easily out-of-sync.
• Each time we release a new package we need to deploy the website too.
• We have 2 code paths to maintain.
• Balrog is more secure because the client does a CA chain validation.

IOS, Android and Linux will use balrog just to know when there is a new build available. The real update will be done via Google Play, Apple Store, or the PPA repo.

┆Issue is synchronized with this Jira Task ┆Reporter: Data Sync

[data-sync-user]

➤ Sarah Bird commented:

Stale. There's good ideas in here. But ok to close as should get picked elsewhere. Closed during bug squashing.