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.
  2. 20 Jul, 2019 1 commit
  3. 11 Jul, 2019 2 commits
  4. 26 Jan, 2018 1 commit
  5. 16 Nov, 2016 1 commit
  6. 15 Feb, 2016 1 commit
  7. 03 Jan, 2016 1 commit
  8. 22 Nov, 2015 1 commit
  9. 14 Sep, 2015 1 commit
    • Alan's avatar
      Replace Vidalia status icon by a GNOME shell extension · c34e2836
      Alan authored
      To get rid of unmaintained Vidalia, we need to replace its status icon. We add
      a simple shell extension that adds a Tor status icon to the shell top bar. The
      status is defined by the presence of a file that we create in our tor-is-ready
      NetworkManager dispatcher script. This will-fix: #9002.
  10. 29 Mar, 2015 2 commits
  11. 17 Mar, 2015 2 commits
  12. 19 Sep, 2014 2 commits
    • Tails developers's avatar
      Escape dots in regex. · bcd8c314
      Tails developers authored
    • Tails developers's avatar
      Install TBB in a custom way instead of installing Iceweasel. · 3f1a351d
      Tails developers authored
      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.
  13. 04 Aug, 2014 1 commit
  14. 06 Mar, 2014 1 commit
    • Tails developers's avatar
      Start Tor Launcher and time syncing concurrently. · ed6e9f3c
      Tails developers authored
      Having Tor Launcher block will leave it and Tor in a deadlock if the
      system clock is way off. The time syncing stuff has to run in parallel
      to deal with that.
      Unfortunately, in some situations the time syncing script may restart
      Tor, which will make Tor Launcher lose its control port connection,
      leaving it with a dead progress bar. These are:
      1. We failed to get a consensus. In this situation nothing works well
         any way, so whatever we do isn't much of a regression.
      2. We get a consensus, but the system time is outside its interval.
         In this case we're guaranteed to make Tor work.
      The best we can do at the moment seems to be to to simply kill Tor
      Launcher, and ensure that it won't restart upon reconnect. At least
      that deals with 2 in pretty nice manner, while 1 isn't any worse off
  15. 18 Feb, 2014 1 commit
  16. 09 Jan, 2014 2 commits
  17. 08 Jan, 2014 1 commit
    • Tails developers's avatar
      Improve phrasing · b12a1ea9
      Tails developers authored
        - Say "the Internet" as GDP Style Guide
        - 'Access' is a bit more accurate than 'use'
        - Deduplicate 'Tor is ready' and 'now'
  18. 07 Jan, 2014 4 commits
  19. 20 Apr, 2013 1 commit
  20. 02 Oct, 2011 1 commit
    • Tails developers's avatar
      Set time from Tor consensus unless it's already in the valid interval. · 58e1b1a3
      Tails developers authored
      This is based on ideas from Liberte Linux' tordate script,
      and meant to implement
      This allows greatly simplifying the 50-htp.sh NM hook: no need to do fancy
      tricks with /etc/hosts anymore.
      Split out and re-order NM hooks:
        First, setup the firewall.
        Then restart Tor.
        Then set the time using Tor consensus, and start HTP (non-blocking) in the background.
        Eventually, restart and cleanup everything that needs to: ttdnsd, pdnsd,
        Vidalia, etc.
      Doing so allows us to stop passing a tiny DNS timeout to htpdate / wget anymore:
      commit e291af5d, that introduced this "-t 1" option, explains why it was added.
      These reasons don't stand anymore: the IPs of the server queried by htpdate are
      not in /etc/hosts nowadays.
      Non-blocking htpdate has an initscript (/etc/init.d/htpdate, that should not
      start on its own); its options were moved to /etc/default/htpdate.
      The tails-htp-notify-user script is removed: no need for feedback as this is now
      non-blocking and does not prevent actual usage. A bit more KISS does not hurt.