1. 15 Jan, 2021 1 commit
    • anonym's avatar
      Always start Tor Launcher (refs: #17330). · 1ef8d52f
      anonym authored
      In other words, always enable what we used to call "bridge mode",
      i.e. that tor won't touch the network until the user has configured it
      via Tor Launcher.
      
      This also includes changing Tails Greeter's Network Configuration
      setting to only be about whether to enable or disable networking.
      1ef8d52f
  2. 18 Jun, 2020 2 commits
  3. 04 Oct, 2019 1 commit
  4. 11 Jul, 2019 2 commits
  5. 10 Jan, 2016 1 commit
  6. 17 Nov, 2015 1 commit
  7. 09 Nov, 2015 3 commits
  8. 30 Mar, 2015 2 commits
    • intrigeri's avatar
      Import network unblocking steps + NM startup back into /usr/local/sbin/tails-unblock-network. · 3bebc450
      intrigeri authored
      We've previously moved the udevadm mangling out of
      tails-unblock-network.service, but the NM startup handling was left in there.
      So, NM could possibly start before the MAC address has been spoofed, which we
      need to avoid.
      
      Another option would have been to add all of this to PostLogin, but it has so
      little to do with the Greeter's job that I felt it would be nicer to have
      PostLogin simply run a script that does all the work, so that most of it is
      self-contained in our main Git repo. For the same reason, this commit also
      imports the restricted network detector startup in the very same script.
      3bebc450
    • intrigeri's avatar
      Move udevadm stuff to PostLogin/Default. · c0c1cf6a
      intrigeri authored
      Apparently, udevadm calls are not always honored when they're started from
      tails-unblock-network.service, possibly because we started it in a non-blocking
      way.
      c0c1cf6a
  9. 29 Mar, 2015 9 commits