GitLab

The Unsafe Browser camoufalge was broken since the browser profile was
owned by root, no the user running the tails-activate-win8-theme
script, which require that it is writable for that user.

It turns out that the branding's name of the browser can differ quite
a bit between different langpacks, e.g. in Arabic it's written in
Arabic, but in languages using latin based it's often "(Mozilla)?
Firefox". Hence we must set the value according to the key, which is
the saner way, instead of simply replacing values.

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.

Commit dadb276ff drops this operation, and instead only removes the bookmarks
from the already created profile in /home/clearnet. This is incorrect (and
apparently untested): when no bookmarks exist on Firefox startup, it imports
the default ones from the system-wide profile skeleton.

So, here we remove bookmarks from both places.

The Search Bar is removed in the Windows 8 camouflage, so having
Wikipedia as the default cannot be used as a stealthy visual indicator
any more. We already have "Unsafe Browser" in both the window title,
and the button to the right of the URL box, which should make it clear
enough which browser is used.

If we're in camouflage mode we want it to be applied to the Unsafe
Browser as well. However, the camouflage activation script modifies
the *user's* own profile, not the system one, so it must be present at
this point, and then it's easier to also make all the other changes to
the user's profile since any changes to the system profile will not be
copied back in.

Running `notify-send` as root doesn't show anything, so we fallback on
our reliable `tilas-notify-user` instead.

It does not need Tor to be ready.

This function is not used anywhere, and obviously was not even tested, given the
typo (${dialob_text}) it contains.

GSettings can't be set with sudo from GDM's PostLogin on Wheezy (tried both with
"gsettings set" and "dconf write"), so we'll have to do this otherwise.

Then:

* Adapt the Unsafe Browser script accordingly: make it run
  tails-activate-winxp-theme as the clearnet user. This likely won't work
  either, for the same reason as why we're doing this entire commit at all,
  so likely this one will need more adaptation. We'll see.

* Don't try to delete /etc/skel/Desktop/*.desktop: it seems entirely useless
  (the users we need have already been created) and can't work now that we don't
  run this script as root anymore.

Else, the Unsafe Browser complains that "Iceweasel is configured to use a proxy
server that can't be found." and cannot connect to the Internet.

They have just moved to 000-tor-browser.js. I don't want to have to adapt this
script every time it happens.

Mozilla's .ja and .jar files are now optimized in a way that makes it basically
non-standard ZIP archives. 7z can't read them, so let's switch to unzip, that
warns and cries but manages to handle it (still have to ignore its non-zero exit
code, but well).

So, we need to install unzip.

https://bugzilla.mozilla.org/show_bug.cgi?id=605524
https://bugzilla.mozilla.org/show_bug.cgi?id=595473

See todo/buggy_aufs_vs_unsafe-browser.

When network.proxy.type=0 and some other network.proxy.* is set in
user.js, Iceweasel behaves weirdly, so we make sure only
network.proxy.type=0 is set.

First we have the /live -> /lib/live move, but some stuff in there has
also been reorganized.

If Vidalia is running, and Tor is restarted, then we also want to
restart Vidalia. This is because Vidalia doesn't re-connect to Tor
automatically, so the user has to restart it to be able to control Tor
again. Also, any options set by Vidalia will be lost since they
weren't written to torrc, which causes Tor to reach an inactive state
if it's restarted in "bridge mode".

This refers to e.g. the name displayed in the window title bar.

No addons are essential for the Unsafe Browser's intent. If anything
they will modify the network fingerprint compared to a normal Iceweasel
install, which is undesirable.

Now camouflage mode isn't set on the kernel cmdline, but via an option
in tails-greeter.