1. 08 Mar, 2017 2 commits
  2. 02 Mar, 2017 2 commits
  3. 28 Feb, 2017 1 commit
    • anonym's avatar
      Completely remove I2P. · e9d02049
      anonym authored
      We have decided to remove I2P (Refs: #11276) due to our failure of
      finding someone interested in maintaining it in Tails.
      Will-fix: #12263
  4. 20 Feb, 2017 1 commit
  5. 25 Jan, 2017 1 commit
    • anonym's avatar
      Add optional pause() notification feature to the test suite. · 9bdf05e4
      anonym authored
      It will run an arbitrary shell command when pause() is called, e.g. on
      failure when --interactive-debugging is used. This is pretty useful
      when multitasking with long test suite runs, so you immediately are
      notified when a test fails (or when you reached a temporary pause()
      Will-fix: #12175
  6. 17 Nov, 2016 2 commits
  7. 02 Nov, 2016 1 commit
    • anonym's avatar
      Improve exception handling in the remote shell. · 8769946c
      anonym authored
      For now, let's just focus on remote shell timeouts, and for that let's
      be really sure we only catch *remote shell* timeouts, and not try_for()
      timeouts thrown from "outside" when wrapping around remote shell usage.
  8. 01 Nov, 2016 1 commit
    • anonym's avatar
      Make all remote shell usage timeout. · e300ae63
      anonym authored
      ... after 20 minutes, by default, and it is no coincidence that it is
      distinctly lower than our Jenkins' setup's timeout. For commands that
      may require longer timeout (or none) there's an option.
  9. 31 Oct, 2016 1 commit
    • anonym's avatar
      Issue ASCII bell when the test suite pause():es. · f3362f9a
      anonym authored
      Most terminal emulators will send a notification of some sort when and
      ASCII bell is received, which is pretty helpful for --pause-on-fail, and
      if you add temporary pause():es while debugging.
  10. 29 Aug, 2016 1 commit
  11. 28 Aug, 2016 1 commit
  12. 22 Apr, 2016 1 commit
  13. 20 Apr, 2016 2 commits
    • anonym's avatar
      Revert "Simplify by inlining." · a0103997
      anonym authored
      This reverts commit 5dae9681.
      I missed that force_new_tor_circuit() was used elsewhere when I
      removed it in the reverted commit.
    • anonym's avatar
      Completely rewrite the firewall leak detector. · c2a2465c
      anonym authored
      The old design was very inflexible, which over time lead to the
      implementation growing messy as different checks were added. The
      issue was that it had to hard-code the particular checks we
      wanted, and did not allow the user to formulate an expression for
      which packets are considered leaks or not. So, let's instead
      provide an assertion-like function to which the user passes a
      block describing how we want all our packets to look.
      Furthermore, now all firewall leak tests should be ok with the
      simulated Tor network provided by Chutney. Since all Tor nodes
      (incl. bridges) run from the same host (and IP address) we also
      include the server port when verifying that no unexpected hosts were
      Note that in some cases we've lost a bit of information and
      precision, e.g. among the anti-tests we no longer exactly match
      the protocol that was leaked, but that wasn't very valuable to
      begin with, and instead we test *exactly* the code that these are
      anti tests for -- a true anti test, indeed!
      Also, the 'no traffic has flowed to the LAN' (now renamed) had a
      serious bug which was fixed in passing -- the `@lan_host`
      variable was not set, so it is `nil`, which could never be among
      the IPv4 TCP leaks, so that step always succeeded! :S
  14. 15 Apr, 2016 1 commit
    • anonym's avatar
      Make it possible to make Tails use a simulated Tor network. · 139c3ace
      anonym authored
      ... provided by Chutney (https://gitweb.torproject.org/chutney.git).
      This is enabled iff the local configuration contains something like:
          src_dir: "/path/to/chutney-src-tree"
      otherwise we'll use the real Tor network as we done previously.
      The main motivation here is improved robustness -- since the "Tor
      network" we now use will exit from the host running the automated test
      suite, we won't have to deal with Tor network blocking. Performance
      should also be improved.
      Will-fix: #9521
  15. 07 Dec, 2015 2 commits
  16. 17 Nov, 2015 1 commit
  17. 28 Oct, 2015 1 commit
  18. 26 Oct, 2015 1 commit
  19. 13 Oct, 2015 1 commit
  20. 06 Oct, 2015 3 commits
  21. 04 Oct, 2015 1 commit
  22. 03 Oct, 2015 1 commit
  23. 25 Sep, 2015 1 commit
  24. 21 Sep, 2015 3 commits
  25. 10 Sep, 2015 1 commit
  26. 09 Sep, 2015 1 commit
    • anonym's avatar
      Refactor "retry Tor" code. · 35ee5cf3
      anonym authored
      There's some code simplification too, and the removal of the
      @new_circuit_tries counter, which is all over the place and is a bit
      hard to keep track of.
      Also for the wget/whois test we do not try to detect if Tor was the
      problem and only force a new circuit (and hence count it as a retry),
      since that could lead to an infinite loop. With the new helper, we
      always do MAX_NEW_TOR_CIRCUIT_RETRIES number of retries.
  27. 07 Sep, 2015 1 commit
  28. 16 May, 2015 1 commit
  29. 29 Apr, 2015 2 commits
    • anonym's avatar
      Allow nested try_for() (Will-fix: #9290) · 2e4c214c
      anonym authored
      I fear we'll get some very hard to debug errors if this limitation is
      forgotten some time in the future, so let's be proactive. Also, switch
      back to throwing Timeout::Error on failure, since it basically is a
      wrapper around it.
    • anonym's avatar
      Fix typo. · b849d2b3
      anonym authored
  30. 17 Apr, 2015 1 commit