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\nin response to a
- Run my own SOCKS5 implementation on
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.
TOR_SOCKS_PORT=9150 in the env var makes everything work, which puzzles me.