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
  • #16220

Closed (moved)
Open
Opened May 27, 2015 by Yawning Angel@yawning

Torbutton/Torlauncher flips out if TOR_SKIP_LAUCH is set without TOR_SOCKS_PORT

Might be kind of hard to test since I encountered this with some kind of sketchy alpha code I'm writing.

What I do:

  • Run my own control port implementation (basically a modified or-ctl-filter) on 127.0.0.1:9151. This implementation returns 250-net/listeners/socks="127.0.0.1:9150"\r\n250 OK\r\n in response to a GETINFO net/listeners/socks request.
  • Run my own SOCKS5 implementation on 127.0.0.1:9150.
  • Set TOR_SKIP_LAUNCH=1 (as the only Tor Browser env var).

What I expect to happen: Tor Browser should think that Tor is running.

What I get: The "Something went wrong" grey screen.

Setting TOR_SOCKS_PORT=9150 in the env var makes everything work, which puzzles me.

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