[tor-bugs] #16220 [Tor Browser]: Torbutton/Torlauncher flips out if TOR_SKIP_LAUCH is set without TOR_SOCKS_PORT

Wed May 27 20:57:01 UTC 2015

#16220: Torbutton/Torlauncher flips out if TOR_SKIP_LAUCH is set without
TOR_SOCKS_PORT
-------------------------+--------------------------
 Reporter:  yawning      |          Owner:  tbb-team
     Type:  defect       |         Status:  new
 Priority:  normal       |      Milestone:
Component:  Tor Browser  |        Version:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
-------------------------+--------------------------
 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.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16220>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online