1. 11 Feb, 2016 4 commits
    • anonym's avatar
      Move gettext initialization code to the top of shell scripts. · 0be0def5
      anonym authored
      That's what we do in most places, so let's be consistent.
    • anonym's avatar
      Avoid set -u issue when testing if variable is set or not. · 364a3c8d
      anonym authored
      Whenever there's a risk that we will reference a shell variable in a
      script run with `set -u` (including libraries that we sources from
      such scripts) we must reference the variable in a way so it gets a
      default value, i.e. `${VAR:-}` to give it the empty string as the
      default (which is what generally makes sense).
      In particular, it's quite clear that in all cases where we do
      something like `[ -n "${VAR}" ]` or `[ -z "${VAR}" ]`, where an
      expected value is the empty string, which could mean that the variable
      is not initialized, we should give such a default (as the empty
    • anonym's avatar
      Also set -e in some scripts. · bbc2d6ca
      anonym authored
    • anonym's avatar
      Add set -u to all gettext:ized shell scripts. · 74a91c28
      anonym authored
      In gettext-base < 1.8.2, like the one we had in Wheezy, gettext.sh
      references the environment variable ZSH_VERSION, which we do not
      set. This has prevented us from doing `set -u` in all gettext:ized
      shell scripts unless we first initialize that variable before sourcing
      Now that we install a new enough gettext-base, we can finally do this
      and remove the initialization hacks.
      Will-fix: #9371
  2. 10 Feb, 2016 3 commits
    • anonym's avatar
      Do the fontconfig dance with all browsers. · a8021ec0
      anonym authored
      I.e. also the Unsafe and I2P Browser's. The main reason is so we do
      not need different images for these and the Tor browser in the
      automated test suite. One may argue, though, that for the Unsafe
      Browser this list of fonts would be fingerprintable, but I would be
      surprised if it already isn't so due to the Tor Browser Firefox
    • anonym's avatar
      Use an appropriate working directory when launching the Tor Browser. · 4173d78b
      anonym authored
      The Tor Browser assumes that the working directory is the directory
      where the browser lives (e.g. the executable). For instance, the
      fonts.conf (for fontconfig) the Tor Browser uses looks for the fonts
      in the "fonts" sub-directory of the current working directory. This
      will fix issues with "empty boxes" as characters in the Save As/Open
      Will-fix: #11097
    • anonym's avatar
      Propagate Tor Launcher options via the wrapper. · 2fc6d139
      anonym authored
      E.g. for our custom/undocumented (but so far unused)
      `--force-net-config` option.
  3. 09 Feb, 2016 8 commits
  4. 08 Feb, 2016 1 commit
  5. 04 Feb, 2016 4 commits
  6. 26 Jan, 2016 1 commit
  7. 25 Jan, 2016 1 commit
  8. 22 Jan, 2016 1 commit
  9. 11 Jan, 2016 1 commit
  10. 10 Jan, 2016 3 commits
  11. 09 Jan, 2016 3 commits
  12. 05 Jan, 2016 2 commits
  13. 03 Jan, 2016 1 commit
  14. 02 Jan, 2016 1 commit
  15. 18 Dec, 2015 1 commit
  16. 14 Dec, 2015 3 commits
  17. 10 Dec, 2015 1 commit
  18. 09 Dec, 2015 1 commit