Skip to content

SETCONF Tor control protocol command should not be used when system Tor is configured / TOR_SKIP_LAUNCH=1 is not honored

Summary

In an environment configured to use operating system managed Tor (i.e. not using Tor Browser's integrated Tor), Tor Browser attempts to use SETCONF Tor control protocol command.

Issue first noticed in 13.5a6

Does not happen with 13.0.13.

Steps to reproduce:

Set environment variables.

export TOR_SKIP_LAUNCH=1
export TOR_USE_LEGACY_LAUNCHER=1
export TOR_SOCKS_IPC_PATH="/run/anon-ws-disable-stacked-tor/127.0.0.1_9150.sock"
export TOR_CONTROL_IPC_PATH="/run/anon-ws-disable-stacked-tor/127.0.0.1_9151.sock"
export TOR_SKIP_CONTROLPORTTEST=1
export TOR_NO_DISPLAY_NETWORK_SETTINGS=1
  1. Start Tor Browser from the command line.

What is the current bug behavior?

Tor Browser attempts to use SETCONF.

What is the expected behavior?

Tor Browser should not attempt to use SETCONF.

Environment

  • Which operating system are you using? For example: Whonix 17
  • Which installation method did you use? download for Linux, extracted to home folder (tb-updater)
  • Affects also Tails? Untested. I would guess so.
  • Affects also other transparent proxy / system Tor / Tor on other computer in LAN setups? Probably. I don't see why not.

Relevant logs and/or screenshots

onion-grater:

command filtered: SETCONF UseBridges=0 Bridge Socks4Proxy Socks5Proxy Socks5ProxyUsername Socks5ProxyPassword HTTPSProxy HTTPSProxyAuthenticator ReachableAddresses