Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13079

Closed (moved)
Open
Opened Sep 07, 2014 by proper@proper

environment variable to skip TorButton control port verification

Tor Button now does its own Tor ControlPort verification.

Source #6546 comment:33 mikeperry:

TBB now performs its own control port verification. We simply check that the socks port Tor says its on is the one Firefox is configured to use.

If that test fails, the default homepage about:tor will show:

Something Went Wrong!
Tor is not working in this browser.

This is problematic in transparent / isolating proxy environments, that do not wish to allow ControlPort access for security reasons (getinfo address and other dangerous ControlPort commands).

The test is implemented in torbrowser.js, in function torbutton_local_tor_check().

[...]
  const kCmdArg = "net/listeners/socks";
[...]
  let resp = torbutton_send_ctrl_cmd("GETINFO " + kCmdArg + "\r\n");
[...]

(The environment variable TOR_SKIP_LAUNCH=1 does not prevent this. [No such variable in Tor Button's source code.])

It would be nice if there was an environment variable such as TOR_SKIP_CONTROLPORTTEST (or so), that would skip this test.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13079