1. 04 May, 2016 1 commit
    • anonym's avatar
      Always run the 'the Tails desktop is ready' step. · fc777723
      anonym authored
      ... after logging in via Tails Greeter. Now we do some very important
      stuff there, like enabling the accessibility toolkit in GNOME. That is
      specifically something we lose if we forgot to run that step after
      rebooting, which specifically was a problem in at least one scenario
      (Deleting a Tails persistent partition).
      While we're at it, let's also run the 'Tails Greeter has dealt with
      the sudo password' step at the same time.
  2. 08 Jan, 2016 2 commits
  3. 07 Dec, 2015 2 commits
  4. 03 Dec, 2015 1 commit
  5. 15 Oct, 2015 2 commits
  6. 06 Oct, 2015 1 commit
    • anonym's avatar
      Improve names of generated snapshot restoring steps. · 83bde0f9
      anonym authored
      Essentially I did:
          sed -i 's/Tails has booted/I have started Tails/' -- \
              features/*.feature features/step_definitions/snapshots.rb
      (although there was a false positive that I had to restore)
  7. 02 Oct, 2015 1 commit
  8. 14 Aug, 2015 1 commit
  9. 13 Aug, 2015 1 commit
  10. 08 Aug, 2015 2 commits
    • intrigeri's avatar
      Test suite: bump timeout. · ef20dc4e
      intrigeri authored
    • anonym's avatar
      Rework how we test AppArmor denials. · 5cb5daf4
      anonym authored
      The basic idea is to first run a "I start monitoring the AppArmor log"
      step, which records the current time, and that any "AppArmor has
      denied" step run for the same profile later will only look at entries
      from that time and on. The wordings on the steps now make the
      scenarios a bit clearer, and we also don't have to clear syslog any
      more as an ugly workaround.
      Furthermore, this will bring us close to a clean solution of #9924,
      which will require us to run a sysctl command *before* anything that
      could generate the AppArmor log entries we're interested in. The "I
      monitor" step is a perfect candidate for that, wereas we before would
      need yet another step.
  11. 05 Aug, 2015 6 commits
  12. 04 Aug, 2015 1 commit
  13. 11 Jul, 2015 1 commit
  14. 02 Jul, 2015 1 commit
  15. 29 Jun, 2015 1 commit
    • anonym's avatar
      Directly verify apparmor blocking of the Tor Browser. · 36cb0492
      anonym authored
      ... by looking in the audit log. This way we actually know that
      apparmor denied the operation, and so we don't get false positives of
      some classes of errors (e.g. the file simply has wrong permission or
      Since we migrated to a browser based on Firefox esr38 we no longer get
      any graphical feedback for the apparmor blocking, which is the actual
      reason for implementing this.
  16. 03 Jun, 2015 4 commits
  17. 28 May, 2015 2 commits
  18. 27 May, 2015 1 commit
  19. 15 May, 2015 2 commits
  20. 14 May, 2015 1 commit
  21. 05 May, 2015 1 commit
  22. 10 Apr, 2015 2 commits
    • anonym's avatar
      Actually run a web server on the LAN. · 709c9c75
      anonym authored
      It shouldn't be needed for the Tor Browser test since we check the
      network traffic, but we'll need it when testing the Unsafe Browser, so
      why not?
    • anonym's avatar
      Test that the Tor Browser cannot access LAN resources. · 1d27515e
      anonym authored
      Since no HTTP server is listening on the LAN resource the Tor Browser
      would show the same "Unable to connect" error message even if the
      request wasn't blocked. We should be fine, though, since we check the
      captured traffic. The picture is more of a signal saying that "now the
      network traffic would have been generated *if* the request isn't
      blocked" which we use to know when to check the network capture.
  23. 18 Feb, 2015 1 commit
  24. 12 Feb, 2015 1 commit
    • Tails developers's avatar
      Reorder steps to avoid lost key presses. · 4d985860
      Tails developers authored
      First we start the Tor Browser, then we run the step 'there is a GNOME
      bookmark for the amnesiac Tor Browser directory' which opens the GNOME
      Places menu. It seems this may cause the Ctrl+S key presses in the
      next step 'I can save the current page as "index.html" to the default
      downloads directory' to not reach the Tor Browser, but probably get
      lost in the Places menu before it closes from the Esc key press
      (Sikuli is fast!), so the step fails. The new step ordering prevents
      this from happening.
  25. 10 Feb, 2015 1 commit