1. 21 Jul, 2019 1 commit
    • segfault's avatar
      tailslib: Add tor_has_boostrapped() · d9dd9d35
      segfault authored
      I add this function to a new file systemd.sh instead of tor.sh, to make
      it clear that this uses the systemd unit instead of communicating with
      the Tor control socket (which is what tor.sh does).
      
      This function should be used over tor_is_working() from tor.sh in
      scripts which don't already communicate with the Tor control socket.
      d9dd9d35
  2. 20 Jul, 2019 1 commit
  3. 11 Jul, 2019 2 commits
  4. 05 Jan, 2019 1 commit
  5. 18 Aug, 2018 1 commit
  6. 06 Jul, 2018 1 commit
    • intrigeri's avatar
      Make Tor Browser less memory-hungry on systems with less than 3 GiB of RAM (refs: #15716). · 37e14889
      intrigeri authored
      With 2 GiB of RAM, the default settings (4 content child processes) make Tor
      Browser eat way too much memory: Tor Browser starts breaking after some browsing
      and our check for upgrades may fail. With 3 GiB of RAM and the default settings,
      once I open a bunch of tabs, start LibreOffice, Thunderbird, Files and KeePassX,
      then the system still works and Tor Browser is still snappy.
      37e14889
  7. 01 Mar, 2017 3 commits
  8. 06 Oct, 2016 1 commit
  9. 14 Mar, 2016 1 commit
  10. 19 Feb, 2016 1 commit
  11. 11 Feb, 2016 1 commit
    • 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
      gettext.sh.
      
      Now that we install a new enough gettext-base, we can finally do this
      and remove the initialization hacks.
      
      Will-fix: #9371
      74a91c28
  12. 10 Feb, 2016 2 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
      patches.
      a8021ec0
    • 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
      dialoges.
      
      Will-fix: #11097
      4173d78b
  13. 09 Feb, 2016 1 commit
  14. 26 Jan, 2016 1 commit
  15. 03 Jan, 2016 1 commit
  16. 30 Nov, 2015 1 commit
  17. 22 Nov, 2015 1 commit
  18. 18 Nov, 2015 1 commit
    • anonym's avatar
      Remove useless code. · 598a0bf1
      anonym authored
      We only intend to run these script from environments where XAUTHORITY
      is set. Also, there is no ~/.Xauthority.
      598a0bf1
  19. 08 Sep, 2015 2 commits
  20. 18 Jul, 2015 2 commits
  21. 11 Jul, 2015 1 commit
  22. 27 Apr, 2015 1 commit
  23. 29 Mar, 2015 1 commit
  24. 15 Oct, 2014 5 commits
  25. 14 Oct, 2014 1 commit
  26. 02 Oct, 2014 1 commit
  27. 01 Oct, 2014 1 commit
  28. 29 Sep, 2014 1 commit
  29. 24 Sep, 2014 2 commits