1. 15 Sep, 2020 7 commits
    • Alex Catarineu's avatar
      6ae23a1d
    • Kathleen Brade's avatar
      Bug 21431: Clean-up system extensions shipped in Firefox · dad63721
      Kathleen Brade authored
      Only ship the pdfjs extension.
      dad63721
    • Georg Koppen's avatar
      Bug 16285: Exclude ClearKey system for now · c8578096
      Georg Koppen authored
      In the past the ClearKey system had not been compiled when specifying
      --disable-eme. But that changed and it is even bundled nowadays (see:
      Mozilla's bug 1300654). We don't want to ship it right now as the use
      case for it is not really visible while the code had security
      vulnerabilities in the past.
      c8578096
    • Kathleen Brade's avatar
      Bug 4234: Use the Firefox Update Process for Tor Browser. · 12b3435d
      Kathleen Brade authored
      The following files are never updated:
        TorBrowser/Data/Browser/profiles.ini
        TorBrowser/Data/Browser/profile.default/bookmarks.html
        TorBrowser/Data/Tor/torrc
      Mac OS: Store update metadata under TorBrowser/UpdateInfo.
      Removed the %OS_VERSION% component from the update URL (13047) and
        added support for minSupportedOSVersion, an attribute of the
        <update> element that may be used to trigger Firefox's
        "unsupported platform" behavior.
      Hide the "What's new" links (set app.releaseNotesURL value to about:blank).
      Windows: disable "runas" code path in updater (15201).
      Windows: avoid writing to the registry (16236).
      Also includes fixes for tickets 13047, 13301, 13356, 13594, 15406,
        16014, 16909, 24476, and 25909.
      
      Also fix Bug 26049: reduce the delay before the update prompt is displayed.
      Instead of Firefox's 2 days, we use 1 hour (after which time the update
      doorhanger will be displayed).
      
      Also fix bug 27221: purge the startup cache if the Tor Browser
      version changed (even if the Firefox version and build ID did
      not change), e.g., after a minor Tor Browser update.
      
      Also fix 32616: Disable GetSecureOutputDirectoryPath() functionality.
      
      Bug 26048: potentially confusing "restart to update" message
      
      Within the update doorhanger, remove the misleading message that mentions
      that windows will be restored after an update is applied, and replace the
      "Restart and Restore" button label with an existing
      "Restart to update Tor Browser" string.
      
      Bug 28885: notify users that update is downloading
      
      Add a "Downloading Tor Browser update" item which appears in the
      hamburger (app) menu while the update service is downloading a MAR
      file. Before this change, the browser did not indicate to the user
      that an update was in progress, which is especially confusing in
      Tor Browser because downloads often take some time. If the user
      clicks on the new menu item, the about dialog is opened to allow
      the user to see download progress.
      
      As part of this fix, the update service was changed to always show
      update-related messages in the hamburger menu, even if the update
      was started in the foreground via the about dialog or via the
      "Check for Tor Browser Update" toolbar menu item. This change is
      consistent with the Tor Browser goal of making sure users are
      informed about the update process.
      
      Removed #28885 parts of this patch which have been uplifted to Firefox.
      12b3435d
    • Alex Catarineu's avatar
      Bug 10760: Integrate TorButton to TorBrowser core · b4c5d90c
      Alex Catarineu authored
      Because of the non-restartless nature of Torbutton, it required
      a two-stage installation process. On mobile, it was a problem,
      because it was not loading when the user opened the browser for
      the first time.
      
      Moving it to tor-browser and making it a system extension allows it
      to load when the user opens the browser for first time.
      
      Additionally, this patch also fixes Bug 27611.
      
      Bug 26321: New Circuit and New Identity menu items
      
      Bug 14392: Make about:tor behave like other initial pages.
      
      Bug 25013: Add torbutton as a tor-browser submodule
      b4c5d90c
    • Kathleen Brade's avatar
      Bug 28044: Integrate Tor Launcher into tor-browser · 23708264
      Kathleen Brade authored
      Build and package Tor Launcher as part of the browser (similar to
      how pdfjs is handled).
      
      If a Tor Launcher extension is present in the user's profile, it is
      removed.
      23708264
    • Mike Perry's avatar
      TB4: Tor Browser's Firefox preference overrides. · e29c2b2c
      Mike Perry authored
      This hack directly includes our preference changes in omni.ja.
      
      Bug 18292: Staged updates fail on Windows
      
      Temporarily disable staged updates on Windows.
      
      Bug 18297: Use separate Noto JP,KR,SC,TC fonts
      
      Bug 23404: Add Noto Sans Buginese to the macOS whitelist
      
      Bug 23745: Set dom.indexedDB.enabled = true
      
      Bug 13575: Disable randomised Firefox HTTP cache decay user tests.
      (Fernando Fernandez Mancera <ffmancera@riseup.net>)
      
      Bug 17252: Enable session identifiers with FPI
      
      Session tickets and session identifiers were isolated
      by OriginAttributes, so we can re-enable them by
      allowing the default value (true) of
      "security.ssl.disable_session_identifiers".
      
      The pref "security.enable_tls_session_tickets" is obsolete
      (removed in https://bugzilla.mozilla.org/917049)
      
      Bug 14952: Enable http/2 and AltSvc
      
      In Firefox, SPDY/HTTP2 now uses Origin Attributes for
      isolation of connections, push streams, origin frames, etc.
      That means we get first-party isolation provided
      "privacy.firstparty.isolate" is true. So in this patch, we
      stop overriding "network.http.spdy.enabled" and
      "network.http.spdy.enabled.http2".
      
      Alternate Services also use Origin Attributes for isolation.
      So we stop overriding
      "network.http.altsvc.enabled" and "network.http.altsvc.oe"
      as well.
      
      (All 4 of the abovementioned "network.http.*" prefs adopt
      Firefox 60ESR's default value of true.)
      
      However, we want to disable HTTP/2 push for now, so we
      set "network.http.spdy.allow-push" to false.
      
      "network.http.spdy.enabled.http2draft" was removed in Bug 1132357.
      "network.http.sped.enabled.v2" was removed in Bug 912550.
      "network.http.sped.enabled.v3" was removed in Bug 1097944.
      "network.http.sped.enabled.v3-1" was removed in Bug 1248197.
      
      Bug 26114: addons.mozilla.org is not special
      * Don't expose navigator.mozAddonManager on any site
      * Don't block NoScript from modifying addons.mozilla.org or other sites
      
      Enable ReaderView mode again (#27281).
      
      Bug 29916: Make sure enterprise policies are disabled
      
      Bug 2874: Block Components.interfaces from content
      
      Bug 26146: Spoof HTTP User-Agent header for desktop platforms
      
      In Tor Browser 8.0, the OS was revealed in both the HTTP User-Agent
      header and to JavaScript code via navigator.userAgent. To avoid
      leaking the OS inside each HTTP request (which many web servers
      log), always use the Windows 7 OS value in the desktop User-Agent
      header. We continue to allow access to the actual OS via JavaScript,
      since doing so improves compatibility with web applications such
      as GitHub and Google Docs.
      
      Bug 12885: Windows Jump Lists fail for Tor Browser
      
      Jumplist entries are stored in a binary file in:
        %APPDATA%\\Microsoft\Windows\Recent\CustomDestinations\
      and has a name in the form
        [a-f0-9]+.customDestinations-ms
      
      The hex at the front is unique per app, and is ultimately derived from
      something called the 'App User Model ID' (AUMID) via some unknown
      hashing method. The AUMID is provided as a key when programmatically
      creating, updating, and deleting a jumplist. The default behaviour in
      firefox is for the installer to define an AUMID for an app, and save it
      in the registry so that the jumplist data can be removed by the
      uninstaller.
      
      However, the Tor Browser does not set this (or any other) regkey during
      installation, so this codepath fails and the app's AUMID is left
      undefined. As a result the app's AUMID ends up being defined by
      windows, but unknowable by Tor Browser. This unknown AUMID is used to
      create and modify the jumplist, but the delete API requires that we
      provide the app's AUMID explicitly. Since we don't know what the AUMID
      is (since the expected regkey where it is normally stored does not
      exist) jumplist deletion will fail and we will leave behind a mostly
      empty customDestinations-ms file. The name of the file is derived from
      the binary path, so an enterprising person could reverse engineer how
      that hex name is calculated, and generate the name for Tor Browser's
      default Desktop installation path to determine whether a person had
      used Tor Browser in the past.
      
      The 'taskbar.grouping.useprofile' option that is enabled by this patch
      works around this AUMID problem by having firefox.exe create it's own
      AUMID based on the profile path (rather than looking for a regkey). This
      way, if a user goes in and enables and disables jumplist entries, the
      backing store is properly deleted.
      
      Unfortunately, all windows users currently have this file lurking in
      the above mentioned directory and this patch will not remove it since it
      was created with an unknown AUMID. However, another patch could be
      written which goes to that directory and deletes any item containing the
      'Tor Browser' string.  See bug 28996.
      
      Bug 31396: Disable indexedDB WebExtension storage backend.
      
      Bug 30845: Make sure default themes and other internal extensions are enabled
      
      Bug 28896: Enable extensions in private browsing by default
      
      Bug 31065: Explicitly allow proxying localhost
      
      Bug 31598: Enable letterboxing
      
      Disable Presentation API everywhere
      
      Bug 21549 - Use Firefox's WASM default pref. It is disabled at safer
      security levels.
      
      Bug 32321: Disable Mozilla's MitM pings
      
      Bug 19890: Disable installation of system addons
      
      By setting the URL to "" we make sure that already installed system
      addons get deleted as well.
      
      Bug 22548: Firefox downgrades VP9 videos to VP8.
      
      On systems where H.264 is not available or no HWA, VP9 is preferred. But in Tor
      Browser 7.0 all youtube videos are degraded to VP8.
      
      This behaviour can be turned off by setting media.benchmark.vp9.threshold to 0.
      All clients will get better experience and lower traffic, beause TBB doesn't
      use "Use hardware acceleration when available".
      
      Bug 25741 - TBA: Add mobile-override of 000-tor-browser prefs
      
      Bug 16441: Suppress "Reset Tor Browser" prompt.
      
      Bug 29120: Use the in-memory media cache and increase its maximum size.
      
      Bug 33697: use old search config based on list.json
      
      Bug 33855: Ensure that site-specific browser mode is disabled.
      
      Bug 30682: Disable Intermediate CA Preloading.
      
      Bug 40061: Omit the Windows default browser agent from the build
      e29c2b2c
  2. 14 Aug, 2020 1 commit
  3. 16 Jul, 2020 1 commit
  4. 09 Jul, 2020 3 commits
  5. 02 Jul, 2020 1 commit
  6. 01 Jul, 2020 1 commit
  7. 22 Apr, 2020 1 commit
  8. 21 Apr, 2020 2 commits
  9. 08 Apr, 2020 1 commit
  10. 20 Mar, 2020 1 commit
  11. 16 Mar, 2020 3 commits
  12. 11 Mar, 2020 2 commits
  13. 09 Mar, 2020 1 commit
  14. 05 Mar, 2020 1 commit
  15. 09 Mar, 2020 1 commit
    • Gijs Kruitbosch's avatar
      Bug 1618188 - remove XML backend for plugin and add-on blocklisting,... · f1a04bd3
      Gijs Kruitbosch authored
      Bug 1618188 - remove XML backend for plugin and add-on blocklisting, r=mconley,perftest-reviewers,whimboo
      
      This removes the obsolete backend. Notes on some of the less obvious changes
      made as part of this patch:
      
      - some of the gFoo style getters in Blocklist.jsm were only used by the XML
        version of the blocklist; I've removed them and tried to remove spurious
        settings of those properties in the remaining tests.
      - some utility methods (e.g. distribution information getters) were also only
        used for the XML version (for the update URL).
      - it's no longer necessary to test switching implementations.
      - in browser/base/content/test/plugins/, we ran some tests from two manifests
        in order to run them with both blocklist backends. The simplest way of
        reducing this back down to one was to remove the remote-settings one. If I'd
        been more future-oriented when I created the duplication, perhaps I would
        have moved the XML version out into a different manifest instead, but I
        didn't, so now it looks like we're removing the modern one, whereas really
        we're going to be running the modern one as part of the "normal" tests and
        we're no longer running the "old" tests.
      - removed all mentions I could see of extensions.blocklist.url which is no
        longer used for anything.
      - per https://bugzilla.mozilla.org/show_bug.cgi?id=1016555#c23, updated
        references for the OneCRL timing and how it relates to blocklist updates.
      
      Differential Revision: https://phabricator.services.mozilla.com/D64933
      
      --HG--
      extra : moz-landing-system : lando
      f1a04bd3
  16. 02 Mar, 2020 1 commit
  17. 20 Feb, 2020 1 commit
  18. 12 Feb, 2020 1 commit
    • Dana Keeler's avatar
      bug 1586915 - build osclientcerts in-tree for macOS r=jcj,mstange · 2e7b6304
      Dana Keeler authored
      This patch implements osclientcerts for macOS.
      Because the SDK we build with isn't recent enough, some of the functions we
      need aren't guaranteed to be available. To handle this, we load the Security
      framework at runtime and attempt to locate the symbols we need. If this
      succeeds, then operation proceeds as normal. Otherwise, the module will report
      that there are no certificates/keys available.
      
      Differential Revision: https://phabricator.services.mozilla.com/D59957
      
      --HG--
      extra : moz-landing-system : lando
      2e7b6304
  19. 11 Feb, 2020 1 commit
  20. 07 Feb, 2020 1 commit
    • Dana Keeler's avatar
      bug 1586915 - build osclientcerts in-tree for macOS r=jcj,mstange · 877ec9a1
      Dana Keeler authored
      This patch implements osclientcerts for macOS.
      Because the SDK we build with isn't recent enough, some of the functions we
      need aren't guaranteed to be available. To handle this, we load the Security
      framework at runtime and attempt to locate the symbols we need. If this
      succeeds, then operation proceeds as normal. Otherwise, the module will report
      that there are no certificates/keys available.
      
      Differential Revision: https://phabricator.services.mozilla.com/D59957
      
      --HG--
      extra : moz-landing-system : lando
      877ec9a1
  21. 20 Dec, 2019 1 commit
  22. 16 Dec, 2019 2 commits
  23. 14 Dec, 2019 1 commit
  24. 13 Dec, 2019 2 commits
  25. 14 Nov, 2019 1 commit
    • Gabriele Svelto's avatar
      Bug 1516367 - Move the minidump-analyzer out of the crash reporter application... · 6ff1e8b8
      Gabriele Svelto authored
      Bug 1516367 - Move the minidump-analyzer out of the crash reporter application bundle r=spohl,dmajor
      
      The minidump-analyzer tool was originally conceived to be used from the crash
      report client and as such was installed in the crash reporter client
      application bundle on macOS. It was later adapted to work from Firefox itself
      but this caused linking problems when invoked from the Firefox app bundle.
      This patch moves the minidump-analyzer into the Firefox app bundle and adapts
      the relevant code to find it there.
      
      The minidump-analyzer was also not signed like the rest of our executables and
      this patch addresses that issue too.
      
      Differential Revision: https://phabricator.services.mozilla.com/D52910
      
      --HG--
      extra : moz-landing-system : lando
      6ff1e8b8
  26. 04 Nov, 2019 1 commit