1. 07 Nov, 2016 1 commit
  2. 03 Nov, 2016 1 commit
  3. 20 Oct, 2016 2 commits
  4. 19 Oct, 2016 1 commit
  5. 17 Oct, 2016 3 commits
  6. 14 Oct, 2016 6 commits
  7. 26 Sep, 2016 2 commits
  8. 23 Sep, 2016 1 commit
  9. 15 Sep, 2016 3 commits
  10. 12 Sep, 2016 1 commit
  11. 09 Sep, 2016 4 commits
  12. 08 Sep, 2016 1 commit
  13. 30 Aug, 2016 1 commit
  14. 26 Aug, 2016 1 commit
  15. 25 Aug, 2016 1 commit
    • Kathleen Brade's avatar
      Bug 15852: Remove/synchronize Torbutton SOCKS pref logic · 1b41636c
      Kathleen Brade authored
      Remove the remains of the Torbutton settings panel (which was hidden
      by the fix for bug 14630).
      
      Remove the status bar panel (the status bar was removed in Firefox 4).
      
      Remove the outdated "Disable Torbutton to change these settings"
      message from the Firefox proxy settings dialog.
      
      Change the behavior of the "Restore Defaults" button in the Privacy
      and Security Settings window to no longer reset the browser's proxy
      preferences. Our general philosophy is that if Torbutton does not
      provide a GUI for changing a preference, Torbutton should not modify
      the preference. The exceptions are that Torbutton still supports the
      TOR_SOCKS_PORT and TOR_TRANSPROXY environment variables.
      
      Remove a lot of toggle logic, including extensions.torbutton.tor_enabled
      and related preferences.
      
      Remove the dual cookie jar support since Tor can no longer be turned off.
      
      Rename torbutton_close_on_toggle() to torbutton_close_tabs_on_new_identity().
      
      Remove torbutton_check_socks_remote_dns() since SOCKS remote DNS is
      supported by all modern versions of Firefox.
      
      Remove torbutton_has_good_socks() since it was testing for Firefox 5
      or newer.
      
      Remove unused Firefox version check variables, unused functions, and
      commented out code.
      1b41636c
  16. 19 Aug, 2016 1 commit
  17. 12 Aug, 2016 1 commit
  18. 29 Jul, 2016 1 commit
  19. 28 Jul, 2016 1 commit
  20. 17 Jul, 2016 4 commits
  21. 16 Jul, 2016 1 commit
    • Yawning Angel's avatar
      Bug 8725: Consistently deny redirects to browser/addon internal URLs. · fa67687d
      Yawning Angel authored
      The browser's behavior is different depending on if a given internal
      resource is available or not, regardless of the fact that the actual
      body will not load due to the various safeguards and checks.
      
      This normalizes the behavior by denying all redirects destined for URLs
      with proscribed browser internal schemes (`resource`, `about`, `chrome`).
      fa67687d
  22. 17 Jun, 2016 2 commits
    • Georg Koppen's avatar
      Bug 19417: Clear asmjscache · e264e602
      Georg Koppen authored
      This patch clears the asmjscache (and the IndexedDB storage) on
      New Identity and during start-up. The latter is a suboptimal workaround
      we deploy until the asmjscache is Private Browsing Mode aware.
      InedxedDB storage is not so urgent as IndexedDB is not working in
      Private Browsing Mode anyway.
      e264e602
    • Yawning Angel's avatar
      Bug 8725: Block `chrome://` based fingerprinting with nsIContentPolicy. · ace11cd8
      Yawning Angel authored
      Most addons do not set `contentaccessible=yes`, however behavior should
      be consistent even if such addons are installed.
      
      This does not affect any of the standard addons shipped with Tor Browser, but
      will break user installed addons that depend on actually being able to
      access `chrome://` URLs in this manner.
      ace11cd8