1. 31 May, 2017 1 commit
  2. 22 May, 2017 1 commit
  3. 19 May, 2017 1 commit
  4. 04 May, 2017 2 commits
  5. 11 Apr, 2017 1 commit
  6. 15 Mar, 2017 1 commit
  7. 11 Mar, 2017 1 commit
  8. 05 Jan, 2017 1 commit
  9. 27 Oct, 2016 1 commit
  10. 26 Aug, 2016 1 commit
  11. 24 Aug, 2016 1 commit
  12. 23 May, 2016 1 commit
  13. 11 Feb, 2016 1 commit
  14. 09 Feb, 2016 2 commits
  15. 03 Jan, 2016 1 commit
  16. 23 Nov, 2015 1 commit
  17. 22 Nov, 2015 1 commit
  18. 28 Apr, 2015 1 commit
  19. 01 Apr, 2015 1 commit
    • anonym's avatar
      Install Tor Browser's bundled Torbutton instead of custom .deb. · 402c5834
      anonym authored
      As of Torbutton 1.9.1.0 our extensions.torbutton.test_enabled pref is
      part of upstream, so we don't have to maintain our custom .deb any
      more! Note that we still patch our custom Torbutton with
      0001-restore-status-panel-on-ff4.patch (inherited from Debian's
      packaging) but it seems irrelevant for Tails.
      402c5834
  20. 17 Mar, 2015 1 commit
  21. 20 Feb, 2015 1 commit
  22. 10 Feb, 2015 1 commit
    • Tails developers's avatar
      Run Tor Launcher in an unconfined Firefox. · 8adcfc21
      Tails developers authored
      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.
      8adcfc21
  23. 20 Nov, 2014 1 commit
  24. 20 Oct, 2014 1 commit
  25. 14 Oct, 2014 5 commits
  26. 13 Oct, 2014 4 commits
  27. 10 Oct, 2014 5 commits