[tor-bugs] #30473 [Applications/Tor Launcher]: update Tor Browser proposal 102 to account for Tails team feedback

[Tor Bug Tracker & Wiki]

#30473: update Tor Browser proposal 102 to account for Tails team feedback
---------------------------------------+-----------------------------------
 Reporter:  mcs                        |          Owner:  brade
     Type:  defect                     |         Status:  needs_information
 Priority:  Medium                     |      Milestone:
Component:  Applications/Tor Launcher  |        Version:
 Severity:  Normal                     |     Resolution:
 Keywords:  AffectsTails               |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:
---------------------------------------+-----------------------------------
Changes (by mcs):

 * status:  new => needs_information


Comment:

 Replying to [comment:3 anonym]:
 > Good news! I have managed to get Tor Launcher from Tor Browser 9.0a1
 running successfully in Tails. I just extracted it from `browser/omni.ja`,
 changed the directory layout to what is required and adjusted the paths in
 `chrome.manifest` accordingly.
 >
 > Previously I discussed with geko about adding a pref for disabling Tor
 Launcher, but the `TOR_SKIP_LAUNCH` env var is enough our needs.
 >
 > So, in the end, it seems Tails doesn't need any changes at all to Tor
 Launcher. But this would change if we learn that Firefox 68esr will drop
 XUL standalone support.

 This is good news. Do you prefer the new "extract from omni.ja" approach
 instead of pulling a Tor Launcher tree and running `make standalone`? If
 no one is using `make standalone` I think we should remove it (rather than
 spending time to maintain it).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30473#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online