Document for the Tor Browser team in which ways we are a special downstream
We're shipping and using Tor Browser in a very non-standard manner. One direct consequence is that some changes in Tor Browser, that are fine for everyone else, can break our setup or force us to adjust stuff. The Tor Browser team has shown willingness in the last years to take our "special needs" into account, but how/whether this works relies on a rather fragile combination of factors. For example, a Tor Browser team lead that has our needs in mind can make a big difference.
One basic thing we could do to help the Tor Browser team take our needs into account is to… express these needs :)
One way to do this would be to publish a bullet list of how we're special. Then, in the best case, the Tor Browser folks look at it proactively when they're considering changes; and worst case, we have something we can point them to.
IMO we should put about 1h into this to start with, not more. It's fine if it's a standalone document that is not properly integrated into our design doc (although a link from our design doc to this document might be useful).
#2 Updated by intrigeri about 1 month ago
- Target version set to Tails_4.3
Initial braindump to get things started:
- We ship all langpacks and select the UI language depending on the locale chosen by the user in Tails Greeter.
- We run Tor Launcher separately from Tor Browser.
Rationale: Tor Browser is not allowed to configure tor.
- We use Tor Browser's firefox binary for our Unsafe Browser, which is not torified.
- We ship the uBlock Origin add-on (from Debian). To make this work, we patch stuff in omni.ja so that signature verification is skipped for this add-on.