1. 30 Nov, 2015 1 commit
  2. 25 Nov, 2015 1 commit
  3. 24 Nov, 2015 2 commits
  4. 23 Nov, 2015 1 commit
  5. 20 Nov, 2015 2 commits
    • intrigeri's avatar
      Test suite: report more information when 'systemctl is-system-running' fails. · cee9e02d
      intrigeri authored
      This helped me analyze a failure and find #10591.
      cee9e02d
    • intrigeri's avatar
      Test suite: run ping as root. · 59a55080
      intrigeri authored
      On Jessie, setcap is used by default instead of setuid root for /bin/ping,
      but aufs does not support file capabilities:
      
        $ /sbin/getcap /bin/ping
        Failed to get capabilities of file `/bin/ping' (Operation not supported)
      
        $ /sbin/getcap /lib/live/mount/rootfs/filesystem.squashfs/bin/ping
        /lib/live/mount/rootfs/filesystem.squashfs/bin/ping = cap_net_raw+ep
      
      We could of course make /bin/ping setuid root back, just as it has
      always been, but with our firewall it'll only allow pinging the LAN; for
      now, I'm deciding that the limited usefulness is not worth the security
      implications (even though we confine ping with AppArmor), and ping will
      remain root only for now. We'll see how much sensible complains we get
      during the 2.0 beta and RC phases.
      59a55080
  6. 19 Nov, 2015 2 commits
  7. 18 Nov, 2015 2 commits
  8. 17 Nov, 2015 5 commits
  9. 11 Nov, 2015 6 commits
    • anonym's avatar
      Fix bad conflict resolution. · ee861c3b
      anonym authored
      ee861c3b
    • anonym's avatar
    • anonym's avatar
      Adapt Gnome notification handling for Debian Jessie. · bd2d2bdf
      anonym authored
      When waiting for specific notifications we'll completely depend on
      robust_notification_wait() from now on *and* it will leave other
      notifications unlike the old version.
      
      Will-fix: #8782
      bd2d2bdf
    • anonym's avatar
      Remove scenario. · dc5848a2
      anonym authored
      In Jessie, org.gnome.gnome-screenshot.auto-save-directory is empty
      since the default is sensible, ~/Pictures. To save the removed
      scenario we'd have to set it explicitly, which seems stupid. Besides,
      the 'A screenshot is taken when the PRINTSCREEN key is pressed'
      scenario is already testing that GNOME Screenshot saves into this
      directory, which is enough.
      dc5848a2
    • intrigeri's avatar
      Explicitly use tor@default.service when it's the one we mean. · 1390e8b1
      intrigeri authored
      Tor 0.2.7.x packaging now uses a template systemd unit file,
      and the instance we use is called tor@default.service.
      1390e8b1
    • intrigeri's avatar
      Turn htpdate.service into Type=oneshot. · 9bc8ef56
      intrigeri authored
      I want to use time-sync.target (see systemd.special(7)), so that we can
      order stuff after it.
      
      But with Type=simple, we can't tell when htpdate is done, so we can't
      specify that time-sync.target has not been reached until then. So let's
      use Type=oneshot. But then, 20-time.sh would block until htpdate is
      done, which is not what we want; this is solved by using --no-block when
      restarting the service there.
      9bc8ef56
  10. 09 Nov, 2015 3 commits
    • anonym's avatar
      Remove all automated tests of the Windows camouflage. · 050160e8
      anonym authored
      We don't have a working Windows camouflage in Tails/Jessie. If it's
      eventually implemented we, should restore:
      
      * features/windows_camouflage.feature, and
      * features/step_definitions/windows_camouflage.rb,
      
      possibly with some minor modifications. In all likelihood all images
      will have to be updated.
      
      Refs: #8064
      050160e8
    • anonym's avatar
      Add missing chomp(). · 08ef736f
      anonym authored
      08ef736f
    • anonym's avatar
      Decide memory wiping waiting time on configured RAM. · d450e5ab
      anonym authored
      ... instead of detected RAM. This should only make us wait longer,
      since detected RAM <= configured RAM, so it's safe but potentially an
      increase in runtime.
      
      We actually do this since we often want to run these modified steps
      when the remote shell is not available any more, since Tails is
      shutting down.
      d450e5ab
  11. 02 Nov, 2015 8 commits
  12. 31 Oct, 2015 2 commits
  13. 30 Oct, 2015 4 commits
  14. 29 Oct, 2015 1 commit
    • anonym's avatar
      Split step in a more sane way. · d735e787
      anonym authored
      If we have a step containing an "and" we generally can split it. In
      this the first part is even already an existing step!
      d735e787