GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still and

  1. 09 Nov, 2017 4 commits
    • Kathleen Brade's avatar
      Bug 23262: implement integrated progress bar (Part 2) · 803bf117
      Kathleen Brade authored
      Improve UX by greatly reducing the use of modal alert dialogs. In most
      cases errors are now displayed using one of three techniques:
        1. Via an overlaid error panel.
        2. As a message on the progress panel (with a Reconfigure button).
        3. On a standalone error page within the setup wizard.
      Move "Restart Tor" to a separate panel.
      Fix a problem where showAlert() would fail to display an alert: do not
        try to use a hidden window as the parent for the alert.
      Add a showOrHideElemById() utility function and use it.
    • Kathleen Brade's avatar
      Bug 23262: implement integrated progress bar (Part 1) · 09234581
      Kathleen Brade authored
      Replace the old progress window with a progress page that is part
        of the setup wizard and a progress panel that is part of the
        Network Settings window.
    • Kathleen Brade's avatar
      Bug 23261: implement configuration portion of new Tor Launcher UI · 4f07910c
      Kathleen Brade authored
      Eliminate several wizard pages and include all of the bridge and
        proxy settings on one page.
      Use the new Tor Browser logo.
      Reuse Mozilla's help button from the Firefox hamburger menu and add
        help for the proxy settings..
      In the wizard, use a "pageshow" event listener to show page-specific
        titles and to hide/show the navigation buttons as needed.
      After the user chooses to restart the tor process, display the
        "Waiting for Tor to start" panel.
      When tor is restarted by the user, disable networking so that
        bootstrapping does not begin right away; this allows the user to
        make configuration choices first.
      Do not try to connect to the control port if tor is not running.
    • Georg Koppen's avatar
      Version bump (0.2.13) · 019a6b84
      Georg Koppen authored
  2. 21 Sep, 2017 1 commit
  3. 30 Aug, 2017 1 commit
  4. 29 Aug, 2017 2 commits
  5. 03 Aug, 2017 2 commits
  6. 25 Jul, 2017 1 commit
  7. 01 Jun, 2017 2 commits
  8. 23 May, 2017 1 commit
    • Kathleen Brade's avatar
      Bug 22283: Linux 7.0a4 broken after update · 123a3ed9
      Kathleen Brade authored
      Improve our torrc fixup code to remove all ControlPort and SocksPort
      lines that contain a Unix domain socket, and execute the fixup one
      more time. This corrects a problem where the torrc of alpha channel
      users who transitioned from Unix domain sockets to TCP was left
      with ControlPort and SocksPort lines that contained bad paths (the
      parent directory for the Unix domain socket did not exist).
  9. 12 May, 2017 3 commits
  10. 05 May, 2017 1 commit
    • Kathleen Brade's avatar
      Bug 20761: Tor Browser 6.5a4 is ignoring additional SocksPorts · 5154173e
      Kathleen Brade authored
      When starting tor, pass "+__ControlPort" and "+__SocksPort" in the
      args. This causes Tor Launcher's control and SOCKS ports to be added
      to any ports the user has defined in their torrc and also prevents
      the ports defined by Tor Launcher from being written to torrc.
      Also, perform a one-time removal of the torrc lines that conflict with
      the ports that Tor Launcher will use when starting tor.
      This change depends on the fix for #20956.
  11. 14 Apr, 2017 1 commit
  12. 13 Apr, 2017 1 commit
  13. 12 Apr, 2017 1 commit
    • Georg Koppen's avatar
      Bug 21920: Don't show locale selection dialog · afb9893b
      Georg Koppen authored
      The locale selection dialog was one of the features we included in the
      hardened series. It is not needed on the alpha or stable channel. We
      therefore disable it, keeping the code as we might be able to resue it
      for #17400 later on.
  14. 12 Mar, 2017 1 commit
  15. 26 Jan, 2017 1 commit
  16. 16 Jan, 2017 1 commit
  17. 14 Nov, 2016 1 commit
  18. 10 Nov, 2016 1 commit
  19. 02 Nov, 2016 1 commit
  20. 27 Oct, 2016 1 commit
    • Kathleen Brade's avatar
      Bug 20185: Avoid using Unix domain socket paths that are too long · 4dd8f613
      Kathleen Brade authored
      Enforce a maximum length of 100 for Unix domain socket paths.
      If $XDG_RUNTIME_DIR is set, create a unique subdirectory within that
        directory and place the control and SOCKS sockets there if the
        resulting paths will not be too long
      else if the length of <tor-data-dir>/control.socket is less than 100
        characters, place both sockets under <tor-data-dir> (this is compatible
        with the Tor Browser 6.5a3 behavior)
      else create a unique subdirectory under /tmp and place the sockets there.
      The unique subdirectory that is created under $XDG_RUNTIME_DIR or /tmp
      will be named Tor if no such directory exists; otherwise, an integer
      suffix will be appended until a new, uniquely named directory is found
      such as /tmp/Tor-1.
      Also, when starting tor, only include a SocksPort argument if a Unix
      domain socket path or a host/port is available.
  21. 26 Oct, 2016 1 commit
    • Kathleen Brade's avatar
      Bug 20429: Do not open progress window if TOR_SKIP_LAUNCH=1 · c12d5647
      Kathleen Brade authored
      After saving tor settings, if TOR_SKIP_LAUNCH=1 or if
      extensions.torlauncher.start_tor is false, avoid opening the progress
      dialog to monitor bootstrap progress. This avoids displaying a progress
      window that will not make progress (and the situation was made worse by
      the fact that clicking Cancel set DisableNetwork=1).
      Also, leave the network settings dialog open if we fail to set
  22. 20 Oct, 2016 1 commit
    • Kathleen Brade's avatar
      Bug 20111: use Unix domain sockets for SOCKS port by default · 8ca52414
      Kathleen Brade authored
      New preferences:
        extensions.torlauncher.socks_port_use_ipc (Boolean; defaults to true)
        extensions.torlauncher.socks_ipc_path (override default IPC path)
        extensions.torlauncher.socks_port_flags (SocksPort flags)
      Also added support for the TOR_SOCKS_IPC_PATH environment variable.
      Consistently use IPC to refer to Unix domain sockets.
      Renamed preferences:
        extensions.torlauncher.control_port_use_socket is now
        extensions.torlauncher.control_socket_path is now
      Renamed the TOR_CONTROL_SOCKET env variable to TOR_CONTROL_IPC_PATH.
      Change _strUnescape() to throw and fix hex and octal unescaping.
  23. 28 Sep, 2016 1 commit
  24. 15 Sep, 2016 1 commit
  25. 06 Sep, 2016 1 commit
  26. 01 Sep, 2016 1 commit
  27. 31 Aug, 2016 1 commit
    • Kathleen Brade's avatar
      Bug 14272: Make Tor Launcher work with Unix Domain Socket option · 8871259c
      Kathleen Brade authored
      On non-Windows platforms, use a Unix domain socket by default for the
      Tor control port. New preferences:
        extensions.torlauncher.control_port_use_socket (Boolean)
        extensions.torlauncher.control_socket_path (path string)
      New environment variable: TOR_CONTROL_SOCKET
      When starting tor, always include a ControlPort argument so that
      users can use environment variables to switch between the two control
      port types.
      Add a public TorGetControlSocketFile() function that Torbutton will
      use to retrieve the socket file (an nsIFile) when a Unix domain
      socket is in use.
      Moved the getTorFile() function to our utilities module.
  28. 12 Jul, 2016 1 commit
  29. 24 Jun, 2016 1 commit
  30. 05 Jun, 2016 1 commit
  31. 16 May, 2016 1 commit
  32. 25 Apr, 2016 1 commit