1. 17 Jun, 2013 1 commit
  2. 16 Jun, 2013 1 commit
  3. 03 May, 2013 1 commit
  4. 13 Dec, 2012 1 commit
  5. 21 Nov, 2012 1 commit
  6. 20 Nov, 2012 1 commit
  7. 09 Oct, 2012 1 commit
  8. 08 Oct, 2012 1 commit
  9. 22 Aug, 2012 1 commit
  10. 19 Aug, 2012 1 commit
  11. 07 Jun, 2012 1 commit
  12. 29 Mar, 2012 1 commit
  13. 28 Mar, 2012 1 commit
  14. 22 Mar, 2012 1 commit
  15. 30 Dec, 2011 2 commits
  16. 17 Dec, 2011 1 commit
  17. 13 Dec, 2011 1 commit
  18. 05 Dec, 2011 1 commit
  19. 27 Nov, 2011 2 commits
  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
      https://tails.boum.org/todo/remove_the_htp_user_firewall_exception/
      
      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.
      58e1b1a3
  21. 09 Jul, 2011 1 commit
    • Tails developers's avatar
      Build and install documentation into the chroot. · 4cb04c88
      Tails developers authored
      Rationale: our static website cannot be copied to a FAT32 filesystem
      due to filenames being too long. Changing this would be a pain.
      Hence building and installing it into the chroot (-> filesystem.squashfs)
      rather than into the binary_local-includes (-> iso9660 / FAT32 filesystem).
      
      This means the documentation cannot be browsed offline from outside Tails.
      However, our installer creates GPT hidden partitions, so the doc would not be
      browseable from outside Tails anyway. The only usecase we really break by doing
      so is browsing the documentation while running a non-Tails system, from a Tails
      CD.
      4cb04c88
  22. 29 Apr, 2011 1 commit
  23. 02 Mar, 2011 2 commits
  24. 23 Dec, 2010 1 commit
  25. 20 Nov, 2010 1 commit
  26. 20 Oct, 2010 3 commits
  27. 16 Oct, 2010 3 commits
  28. 03 Oct, 2010 1 commit
  29. 02 Oct, 2010 2 commits
  30. 30 Sep, 2010 1 commit
  31. 25 Sep, 2010 2 commits