1. 11 Feb, 2016 3 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.
      0be0def5
    • 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
      string).
      364a3c8d
    • 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
  2. 10 Feb, 2016 1 commit
  3. 09 Feb, 2016 5 commits
    • anonym's avatar
      Remove no longer relevant cleanup procedure. · 0f79c3dc
      anonym authored
      The path hasn't existed for a long while, and places.sqlite hasn't
      been created there for even longer.
      0f79c3dc
    • anonym's avatar
      Move Tor Launcher env configuration. · 695ccf8a
      anonym authored
      It feels like it belongs better in the script where we actually start
      Tor Launcher than the wrapper that makes root invoke it in the way we
      want. Also, we have to think less about how sudo propagates
      environment variables so we can simplify its setup.
      695ccf8a
    • anonym's avatar
      Move tor-launcher-standalone into /usr/local/lib. · 06bc2513
      anonym authored
      ... where we have the Tor Browser. For consistency.
      06bc2513
    • anonym's avatar
      Move tor-launcher script tor /usr/local/bin. · 42b1cf44
      anonym authored
      Let's not pretend the current script is similar to what upstream would
      use, since it has Tails specific stuff in it.
      42b1cf44
    • anonym's avatar
      Make the -profile Tor Launcher workaround simpler. · 2db6d171
      anonym authored
      ... instead of the crazy workaround we had to use before. It turns out
      you *can* use -app and -profile together, but only if -profile is
      given last. It may be that it was fixed recently, because I'm pretty
      sure it didn't work last time I wroked on this.
      
      Also, in /usr/share/TorBrowser/Data/Browser (which is the "default"
      profile directory relative to the Tor Launcher applocation.ini file)
      the Caches directory must exist and be accessible for the tor-launcher
      user even if -profile is used, so we just have to ensure it exists.
      
      Will-fix: #7943
      2db6d171
  4. 10 Jan, 2016 1 commit
  5. 09 Dec, 2015 1 commit
  6. 07 Dec, 2015 3 commits
  7. 30 Nov, 2015 8 commits
  8. 24 Nov, 2015 2 commits
  9. 19 Nov, 2015 1 commit
  10. 18 Nov, 2015 3 commits
  11. 17 Nov, 2015 4 commits
  12. 11 Nov, 2015 2 commits
  13. 01 Nov, 2015 2 commits
    • bertagaz's avatar
      Fix for real the logical bug for real-only persistence. · 5666ebcb
      bertagaz authored
      The problem was not that live-persist must error out when read-only
      persistence is activated rather than issue a warning. In the bug raised
      by #10431, the problem was that it *already did* because it tried to
      make the new persistence config anyway. So fixing #10431 by erroring out
      just lead to the same situation.
      
      In this case, we don't want to error out but warn out that the migration did not
      happen, and just go on with the boot without trying to migrate anything.
      
      Will-fix: #10431
      5666ebcb
    • bertagaz's avatar
      Fix identation. · c1b46347
      bertagaz authored
      c1b46347
  14. 31 Oct, 2015 1 commit
    • kytv's avatar
      Reorder · e25b4246
      kytv authored
      e25b4246
  15. 30 Oct, 2015 1 commit
  16. 29 Oct, 2015 1 commit
  17. 27 Oct, 2015 1 commit