Skip to content

GitLab

Closed
Created by proper@proper

TorButton about:tor fails when using additional socks listeners

How to reproduce:

  1. Get tor-browser-linux32-3.0-alpha-2_en-US.tar.xz (on Debian Wheezy).

  2. The following ~/tor-browser_en-US/Data/Tor/torrc was used to produce this bug.

# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it

AvoidDiskWrites 1
ControlPort 9151
CookieAuthentication 1
DataDirectory /home/user/tor-browser_en-US/Data/Tor
DirReqStatistics 0
GeoIPFile ./Data/Tor/geoip
Log notice stdout
SocksPort 127.0.0.1:9149
SocksPort 127.0.0.1:9150
SocksPort 192.168.0.31:9151

  1. Change 192.168.0.31 in torrc above to your local LAN IP address.

  2. Start start-tor-browser.

Result:

about:tor will say

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

Expected result:

about:tor says, everything is fine.

Hypothesis:

I think the problem is in torbutton.js, function torbutton_local_tor_check.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information