1. 18 Sep, 2018 2 commits
  2. 11 Sep, 2018 1 commit
  3. 03 Sep, 2018 3 commits
  4. 31 Aug, 2018 1 commit
  5. 30 Aug, 2018 1 commit
  6. 16 Aug, 2018 2 commits
  7. 13 Aug, 2018 1 commit
  8. 31 Jul, 2018 2 commits
  9. 23 Jun, 2018 2 commits
  10. 22 Jun, 2018 2 commits
  11. 21 Jun, 2018 1 commit
  12. 23 May, 2018 1 commit
  13. 22 May, 2018 5 commits
  14. 16 May, 2018 1 commit
  15. 10 May, 2018 1 commit
  16. 07 May, 2018 1 commit
  17. 03 May, 2018 2 commits
  18. 26 Apr, 2018 1 commit
    • Georg Koppen's avatar
      Bug 25807: Change front domain to unbreak Moat · add22769
      Georg Koppen authored
      Google forbids to use www.google.com as front domain now, breaking Moat.
      We change that domain to dontbeevil.appspot.com which seems still to be
      working. That's only a stopgap solution, though, to get Moat unblocked
      for now.
      add22769
  19. 08 Mar, 2018 2 commits
  20. 01 Mar, 2018 1 commit
    • Kathleen Brade's avatar
      Bug 23136: Moat integration (fetch bridges for the user) · e921bb15
      Kathleen Brade authored
      Modify the setup wizard and Network Settings window to allow automated
      retrieval of bridges using Moat, a BridgeDB service which works
      over a meek transport and requires the user to solve a CAPTCHA to
      obtain bridges.
      
      The new tl-bridgedb.jsm JavaScript module handles all communication
      with BridgeDB, and it functions by starting a copy of
      meek-client-torbrowser and operating as a PT client parent process
      (see https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt).
      
      This feature can be disabled (and the Moat-related Tor Launcher UI
      hidden) by setting the pref extensions.torlauncher.moat_service to
      an empty string.
      e921bb15
  21. 21 Feb, 2018 2 commits
  22. 02 Feb, 2018 1 commit
  23. 18 Jan, 2018 1 commit
  24. 17 Jan, 2018 1 commit
  25. 18 Dec, 2017 2 commits