1. 03 Jan, 2016 1 commit
  2. 22 Nov, 2015 1 commit
  3. 15 Apr, 2015 1 commit
    • anonym's avatar
      Make sure the system clock isn't before the build date (Will-fix: #9149). · 88a59388
      anonym authored
      Our live-config hook that imports our signing keys depend on that the
      system clock isn't before the date when the keys where created (sanity
      check by gpg). To avoid this, we ensure (via an early live-config
      hook) that the system clock cannot be before the Tails image build
      date (up to one day, to deal with potential timezone
  4. 06 Mar, 2015 2 commits
  5. 08 Feb, 2015 2 commits
  6. 19 Jan, 2015 2 commits
    • Tails developers's avatar
    • Tails developers's avatar
      Switch to tor+http:// APT sources at boot time instead of at build time (Will-Fix: #8715). · 716fd0b7
      Tails developers authored
      live-build expects to be the only one that manages APT sources.
      Since feature/8194-APT-socks was merged, we're breaking this assumption of its,
      by mangling APT sources under live-build's feet via chroot_local-hooks.
      More specifically, if:
         as is the case when building with Vagrant or when following our manual
         build setup instructions accurately (live-build defaults to
         ftp.de.debian.org for some of its APT configuration),
       * one has dropped .deb's in config/chroot_local-packages, as contributors
         without write access to our APT repository may want to do,
      then after completing the chroot_local-hooks stage, lb_chroot_sources would
      rewrite APT sources to match what we have previously configured (see the check
      at lines 490-498 in live-build 2.x tree), and therefore the ISO image would have
      http:// URLs configured instead of the expected tor+http://.
      Therefore, let's mangle APT sources configuration at boot time instead.
  7. 21 Oct, 2014 1 commit
  8. 27 Sep, 2014 2 commits
  9. 26 Sep, 2014 1 commit
  10. 21 Sep, 2014 1 commit
    • Kill Your TV's avatar
      I2P Browser · bf714344
      Kill Your TV authored
      Browser specifically for I2P based on the scripts that
      configure the "unsafe-browser".
      * Adds a new i2pbrowser user
      * change the I2P menu entry and related sudoers file to start
        this new browser. I2P will be started via NetworkManager (added in a later
        commit) when a user adds 'i2p' to the boot prompt.
      Update I2P firewall rules
      Since the anmesia user won't be browsing eepsites with the Torbrowser
      anymore, and the i2pbrowser user *will* be browsing them, the firewall
      rules needed another update.
      disable cups
      fixes the same problem as ticket #7771 addresses for the
      Remove I2P settings from FoxyProxy
      Since I2P Browser is now used for visiting eepsites (.i2p tld) the I2P
      configs are no longer appropriate for FoxyProxy.
  11. 08 Aug, 2014 2 commits
  12. 05 Aug, 2014 3 commits
  13. 31 Jul, 2014 1 commit
    • Kill Your TV's avatar
      Add an I2P boot parameter · 2eb92957
      Kill Your TV authored
      During the build process, the following are moved to /usr/share/tails:
        - /usr/share/i2p
        - /usr/sbin/wrapper to /usr/share/tails/i2p
        - /usr/share/applications/i2p.desktop to /usr/share/tails/i2p
      The I2P binaries are changed to be owned by i2psvc:i2psvc to prevent it
      being run from the new location under /usr/share/tails/i2p.
      If the string 'i2p' is entered on at the boot prompt, these files are
      returned to ther original locations, making I2P accessible. Also, the
      I2P sudoers file is written to the system, allowing the amnesia user to
      run tails-start-i2p as the i2psvc user.
  14. 25 Jun, 2014 1 commit
  15. 04 Mar, 2014 1 commit
  16. 12 Feb, 2014 1 commit
  17. 17 Jul, 2013 3 commits
  18. 12 Apr, 2013 1 commit
  19. 10 Apr, 2013 2 commits
  20. 14 Feb, 2013 1 commit
  21. 25 Jan, 2013 1 commit
    • Tails developers's avatar
      Use a serial console instead of network for remote shell. · 128f1c3a
      Tails developers authored
      Now we can run commands even without a network connection on the guest
      which some tests depend on. Also, not having to mess with the network
      (especially the firewall) at all is much cleaner and less likely to
      interfere with Tails in unexpected ways.
  22. 02 Dec, 2012 1 commit
  23. 30 Nov, 2012 1 commit
  24. 20 Nov, 2012 1 commit
    • Tails developers's avatar
      Make the default user password-less. · 887a6c0f
      Tails developers authored
      This integrates well with pam e.g. for preventing screen locking to
      completely lock out users who don't set a password in Tails Greeter
      and don't know the default password (which previously was the default
      for Debian Live, namely "live").
  25. 11 Nov, 2012 1 commit
  26. 31 Oct, 2012 1 commit
  27. 24 Sep, 2012 4 commits