[tor-bugs] #13150 [Tor Launcher]: Windows Tor Launcher trying to connect 9151 control port always, instead of using settings

[Tor Bug Tracker & Wiki]

#13150: Windows Tor Launcher trying to connect 9151 control port always, instead of
using settings
----------------------------------+-----------------------
 Reporter:  VasiliyPetrov         |          Owner:  brade
     Type:  defect                |         Status:  new
 Priority:  normal                |      Milestone:
Component:  Tor Launcher          |        Version:
 Keywords:  ControlPort, windows  |  Actual Points:
Parent ID:                        |         Points:
----------------------------------+-----------------------
 Installation package:
 torbrowser-install-3.6.5_en-US.exe
 (v3.6.5)

 I'm trying to start Two Tor Bundle browsers on the same system to have
 different sessions and split a persons (not to mixup them, but to have a
 possibility to browse internet at the same time).

 I had two copies of Tor Browser Bundle Installed.
 For example, the first one is installed to (1):
 X:\Tor Browser\

 The second one is installed to (2):
 X:\Tor Browser 2ND\

 (1) - default settings, nothing is changed. I.e. we will have:
 SocksPort - 9150, ControlPort - 9151, FlashPort - 9000

 (2) - immediately after fresh installation, without starting anything, I
 had edited following files (see "->" symbol):

 [.\Data\Tor\torrc-defaults]
 SocksPort 9150 -> 9250
 ControlPort 9151 -> 9251
 ClientTransportPlugin flashproxy exec Tor\PluggableTransports\flashproxy-
 client --register :0 :9000 -> :9100

 [.\Data\Browser\profile.default\preferences\extension-overrides.js]
 pref("extensions.torbutton.socks_port", 9150 -> 9250);

 So, it seems like second Tor Browser Bundle must use only following ports:
 9250, 9251 and 9100? But... NO!

 What I'm doing?

 1. Starting (1) Tor Browser Bundle. It starts perfect and all is working
 perfect (default settings, default ports). Working in it - all is fine.

 2. Now, without closing the (1) we are trying to start (2) Tor Browser
 Bundle. (All actions are controlled by firewall-process/HIPS to see any
 actions on the machine. And what I will see?
 I'm getting a request to my firewall, that process
 X:\Tor Browser 2ND\Browser\firefox.exe
 is trying to create socket on 127.0.0.1:9250
 OK, it is what we expect.

 But when GUI is starting it is trying to create socket on...
 127.0.0.1:9151 (Default ControlPort) instead of 127.0.0.1:9251
 (ControlPort). WTF?!

 If you will block this try to use this port, you will get a error message:
 ========================
 Tor Launcher
 Could not connect to Tor control port.
 [OK]
 ========================
 and Tor Browser will not be started.

 So, Tor Launcher of (2) using/trying to use 9151 port instead of
 configured 9251!

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