GitLab

Running Tor Launcher with the same AppArmor profile as Tor Browser would force
us to open that profile too broadly. E.g. it requires the ability to run
dbus-daemon, to give an idea.

Given:

 * Tor Launcher runs as a dedicated user
 * Tor Launcher runs very early, at a time when the user likely isn't doing
   anything sensitive to X keystrokes sniffing etc., and closes immediately
   after Tor is ready
 * Tor Launcher offers a very limited set of functionality

=> it seems safe enough to run it unconfined, at least for now.

That way one only has to remember to always call firefox with
exec_firefox(), and not to set LD_LIBRARY_PATH. As an example, this
was forgotten for Tor Launcher, which also was fixed.

Note that the browser profile has been moved location inside the
tarball, and the bundled firefox will look for the default profile
accordingly.

Instead of installing the iceweasel package (and friends) we now fetch
the TBB tarballs at build-time and extract the Tor Browser, browser
add-ons and langpacks, and browser user data into sensible places. We
try to keep something like the old organization as much as possible.

Unfortunately this drops language support to whatever subset that the
TBB supports.