1. 07 Jul, 2022 6 commits
  2. 06 Jul, 2022 2 commits
  3. 05 Jul, 2022 1 commit
  4. 24 Jun, 2022 1 commit
  5. 23 Jun, 2022 1 commit
  6. 21 Jun, 2022 1 commit
  7. 20 Jun, 2022 1 commit
  8. 17 Jun, 2022 8 commits
  9. 16 Jun, 2022 2 commits
  10. 13 Jun, 2022 17 commits
    • Pier Angelo Vendrame's avatar
      Bug 11698: Incorporate Tor Browser Manual pages into Tor Browser · 2edd8bc7
      Pier Angelo Vendrame authored and Richard Pospesel's avatar Richard Pospesel committed
      This patch associates the about:manual page to a translated page that
      must be injected to browser/omni.ja after the build.
      The content must be placed in chrome/browser/content/browser/manual/, so
      that is then available at chrome://browser/content/manual/.
      We preferred giving absolute freedom to the web team, rather than having
      to change the patch in case of changes on the documentation.
      2edd8bc7
    • Pier Angelo Vendrame's avatar
      Bug 40458: Implement .tor.onion aliases · 11a49fb1
      Pier Angelo Vendrame authored and Richard Pospesel's avatar Richard Pospesel committed
      We have enabled HTTPS-Only mode, therefore we do not need
      HTTPS-Everywhere anymore.
      However, we want to keep supporting .tor.onion aliases (especially for
      securedrop).
      Therefore, in this patch we implemented the parsing of HTTPS-Everywhere
      rulesets, and the redirect of .tor.onion domains.
      Actually, Tor Browser believes they are actual domains. We change them
      on the fly on the SOCKS proxy requests to resolve the domain, and on
      the code that verifies HTTPS certificates.
      11a49fb1
    • Alex Catarineu's avatar
      Bug 21952: Implement Onion-Location · f7e77e2c
      Alex Catarineu authored and Richard Pospesel's avatar Richard Pospesel committed
      Whenever a valid Onion-Location HTTP header (or corresponding HTML
      <meta> http-equiv attribute) is found in a document load, we either
      redirect to it (if the user opted-in via preference) or notify the
      presence of an onionsite alternative with a badge in the urlbar.
      f7e77e2c
    • Kathleen Brade's avatar
      Bug 30237: Add v3 onion services client authentication prompt · e0353ab8
      Kathleen Brade authored and Richard Pospesel's avatar Richard Pospesel committed
      When Tor informs the browser that client authentication is needed,
      temporarily load about:blank instead of about:neterror and prompt
      for the user's key.
      
      If a correctly formatted key is entered, use Tor's ONION_CLIENT_AUTH_ADD
      control port command to add the key (via Torbutton's control port
      module) and reload the page.
      
      If the user cancels the prompt, display the standard about:neterror
      "Unable to connect" page. This requires a small change to
      browser/actors/NetErrorChild.jsm to account for the fact that the
      docShell no longer has the failedChannel information. The failedChannel
      is used to extract TLS-related error info, which is not applicable
      in the case of a canceled .onion authentication prompt.
      
      Add a leaveOpen option to PopupNotifications.show so we can display
      error messages within the popup notification doorhanger without
      closing the prompt.
      
      Add support for onion services strings to the TorStrings module.
      
      Add support for Tor extended...
      e0353ab8
    • Richard Pospesel's avatar
      Bug 23247: Communicating security expectations for .onion · 682c8c79
      Richard Pospesel authored
      Encrypting pages hosted on Onion Services with SSL/TLS is redundant
      (in terms of hiding content) as all traffic within the Tor network is
      already fully encrypted.  Therefore, serving HTTP pages from an Onion
      Service is more or less fine.
      
      Prior to this patch, Tor Browser would mostly treat pages delivered
      via Onion Services as well as pages delivered in the ordinary fashion
      over the internet in the same way.  This created some inconsistencies
      in behaviour and misinformation presented to the user relating to the
      security of pages delivered via Onion Services:
      
       - HTTP Onion Service pages did not have any 'lock' icon indicating
         the site was secure
       - HTTP Onion Service pages would be marked as unencrypted in the Page
         Info screen
       - Mixed-mode content restrictions did not apply to HTTP Onion Service
         pages embedding Non-Onion HTTP content
      
      This patch fixes the above issues, and also adds several new 'Onion'
      icons to the mix to indicate all of the various permutations of Onion
      Services hosted HTTP or HTTPS pages with HTTP or HTTPS content.
      
      Strings for Onion Service Page Info page are pulled from Torbutton's
      localization strings.
      682c8c79
    • Mike Perry's avatar
      Omnibox: Add DDG, Startpage, Disconnect, Youtube, Twitter; remove Amazon, eBay, bing · bcd49fe0
      Mike Perry authored and Richard Pospesel's avatar Richard Pospesel committed
      eBay and Amazon don't treat Tor users very well. Accounts often get locked and
      payments reversed.
      
      Also:
      Bug 16322: Update DuckDuckGo search engine
      
      We are replacing the clearnet URL with an onion service one (thanks to a
      patch by a cypherpunk) and are removing the duplicated DDG search
      engine. Duplicating DDG happend due to bug 1061736 where Mozilla
      included DDG itself into Firefox. Interestingly, this caused breaking
      the DDG search if JavaScript is disabled as the Mozilla engine, which
      gets loaded earlier, does not use the html version of the search page.
      Moreover, the Mozilla engine tracked where the users were searching from
      by adding a respective parameter to the search query. We got rid of that
      feature as well.
      
      Also:
      This fixes bug 20809: the DuckDuckGo team has changed its server-side
      code in a way that lets users with JavaScript enabled use the default
      landing page while those without JavaScript available get redirected
      directly to the non-JS page. We adapt the search engine URLs
      accordingly.
      
      Also fixes bug 29798 by making sure we only specify the Google search
      engine we actually ship an .xml file for.
      
      Also regression tests.
      
      squash! Omnibox: Add DDG, Startpage, Disconnect, Youtube, Twitter; remove Amazon, eBay, bing
      
      Bug 40494: Update Startpage search provider
      
      squash! Omnibox: Add DDG, Startpage, Disconnect, Youtube, Twitter; remove Amazon, eBay, bing
      
      Bug 40438: Add Blockchair as a search engine
      
      Bug 33342: Avoid disconnect search addon error after removal.
      
      We removed the addon in #32767, but it was still being loaded
      from addonStartup.json.lz4 and throwing an error on startup
      because its resource: location is not available anymore.
      bcd49fe0
    • Georg Koppen's avatar
      Bug 32658: Create a new MAR signing key · fdc1fc26
      Georg Koppen authored and Richard Pospesel's avatar Richard Pospesel committed
      It's time for our rotation again: Move the backup key in the front
      position and add a new backup key.
      
      Bug 33803: Move our primary nightly MAR signing key to tor-browser
      
      Bug 33803: Add a secondary nightly MAR signing key
      fdc1fc26
    • Kathleen Brade's avatar
      Bug 16940: After update, load local change notes. · 3e6b91f9
      Kathleen Brade authored and Richard Pospesel's avatar Richard Pospesel committed
      Add an about:tbupdate page that displays the first section from
      TorBrowser/Docs/ChangeLog.txt and includes a link to the remote
      post-update page (typically our blog entry for the release).
      
      Always load about:tbupdate in a content process, but implement the
      code that reads the file system (changelog) in the chrome process
      for compatibility with future sandboxing efforts.
      
      Also fix bug 29440. Now about:tbupdate is styled as a fairly simple
      changelog page that is designed to be displayed via a link that is on
      about:tor.
      3e6b91f9
    • Kathleen Brade's avatar
      Bug 13379: Sign our MAR files. · 9da1306c
      Kathleen Brade authored and Richard Pospesel's avatar Richard Pospesel committed
      Configure with --enable-verify-mar (when updating, require a valid
        signature on the MAR file before it is applied).
      Use the Tor Browser version instead of the Firefox version inside the
        MAR file info block (necessary to prevent downgrade attacks).
      Use NSS on all platforms for checking MAR signatures (instead of using
        OS-native APIs, which Mozilla does on Mac OS and Windows). So that the
        NSS and NSPR libraries the updater depends on can be found at runtime,
        we add the firefox directory to the shared library search path on macOS.
        On Linux, rpath is used by Mozilla to solve that problem, but that
        approach won't work on macOS because the updater executable is copied
        during the update process to a location that is under TorBrowser-Data,
        and the location of TorBrowser-Data varies.
      
      Also includes the fix for bug 18900.
      
      Bug 19121: reinstate the update.xml hash check
      
      Revert most changes from Mozilla Bug 1373267 "Remove hashFunction and
      hashValue attributes from nsIUpdatePatch and code related to these
      attributes." Changes to the tests were not reverted; the tests have
      been changed significantly and we do not run automated updater tests
      for Tor Browser at this time.
      
      Also partial revert of commit f1241db6.
      
      Revert the nsUpdateService.js changes from Mozilla Bug 862173 "don't
      verify mar file hash when using mar signing to verify the mar file
      (lessens main thread I/O)."
      
      Changes to the tests were not reverted; the tests have been changed
      significantly and we do not run automated updater tests for
      Tor Browser at this time.
      
      We kept the addition to the AppConstants API in case other JS code
      references it in the future.
      9da1306c
    • Kathleen Brade's avatar
      Bug 4234: Use the Firefox Update Process for Tor Browser. · 47820cbb
      Kathleen Brade authored and Richard Pospesel's avatar Richard Pospesel committed
      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.
      47820cbb
    • Alex Catarineu's avatar
      Bug 27511: Add new identity button to toolbar · fd8984ba
      Alex Catarineu authored and Richard Pospesel's avatar Richard Pospesel committed
      Also added 'New circuit for this site' button to CustomizableUI, but
      not visible by default.
      fd8984ba
    • Richard Pospesel's avatar
      Bug 25658: Replace security slider with security level UI · 9c472fd0
      Richard Pospesel authored
      This patch adds a new 'securitylevel' component to Tor Browser intended
      to replace the torbutton 'Security Slider'.
      
      This component adds a new Security Level toolbar button which visually
      indicates the current global security level via icon (as defined by the
      extensions.torbutton.security_slider pref), a drop-down hanger with a
      short description of the current security level, and a new section in
      the about:preferences#privacy page where users can change their current
      security level. In addition, the hanger and the preferences page will
      show a visual warning when the user has modified prefs associated with
      the security level and provide a one-click 'Restore Defaults' button to
      get the user back on recommended settings.
      
      Strings used by this patch are pulled from the torbutton extension, but
      en-US defaults are provided if there is an error loading from the
      extension. With this patch applied, the usual work-flow of "./mach build
      && ./mach run" work as expected, even if the torbutton extension is
      disabled.
      9c472fd0
    • Matthew Finkel's avatar
      Bug 40253: Explicitly allow NoScript in Private Browsing mode. · 79f6bd71
      Matthew Finkel authored and Richard Pospesel's avatar Richard Pospesel committed
      79f6bd71
    • Arthur Edelstein's avatar
      Bug 12620: TorBrowser regression tests · 95cafa41
      Arthur Edelstein authored and Richard Pospesel's avatar Richard Pospesel committed
      Regression tests for Bug #2950: Make Permissions Manager memory-only
      
      Regression tests for TB4: Tor Browser's Firefox preference overrides.
      
      Note: many more functional tests could be made here
      
      Regression tests for #2874: Block Components.interfaces from content
      
      Bug 18923: Add a script to run all Tor Browser specific tests
      
      Regression tests for Bug #16441: Suppress "Reset Tor Browser" prompt.
      95cafa41
    • Richard Pospesel's avatar
      Bug 27476: Implement about:torconnect captive portal within Tor Browser · 4d174e35
      Richard Pospesel authored
      - implements new about:torconnect page as tor-launcher replacement
      - adds tor connection status to url bar and tweaks UX when not online
      - adds new torconnect component to browser
      - tor process management functionality remains implemented in tor-launcher through the TorProtocolService module
      - adds warning/error box to about:preferences#tor when not connected to tor
      - explicitly allows about:torconnect URIs to ignore Resist Fingerprinting (RFP)
      - various tweaks to info-pages.inc.css for about:torconnect (also affects other firefox info pages)
      
      Bug 40773: Update the about:torconnect frontend page to match additional UI flows
      4d174e35
    • Richard Pospesel's avatar
      Bug 31286: Implementation of bridge, proxy, and firewall settings in about:preferences#connection · 6c67c31e
      Richard Pospesel authored
      This patch adds a new about:preferences#connection page which allows
      modifying bridge, proxy, and firewall settings from within Tor Browser.
      All of the functionality present in tor-launcher's Network
      Configuration panel is present:
      
       - Setting built-in bridges
       - Requesting bridges from BridgeDB via moat
       - Using user-provided bridges
       - Configuring SOCKS4, SOCKS5, and HTTP/HTTPS proxies
       - Setting firewall ports
       - Viewing and Copying Tor's logs
       - The Networking Settings in General preferences has been removed
      
      Bug 40774: Update about:preferences page to match new UI designs
      6c67c31e
    • Pier Angelo Vendrame's avatar
      Bug 40807: Added QRCode.js to toolkit/modules · 98090f27
      Pier Angelo Vendrame authored and Richard Pospesel's avatar Richard Pospesel committed
      98090f27