[tor-bugs] #8378 [Vidalia]: Windows TBB Firefox breaks when Valida calls Tor *not* as ./tor.exe

[Tor Bug Tracker & Wiki]

#8378: Windows TBB Firefox breaks when Valida calls Tor *not* as ./tor.exe
----------------------------+-----------------------------------------------
    Reporter:  cypherpunks  |       Owner:  chiiph  
        Type:  defect       |      Status:  reopened
    Priority:  normal       |   Milestone:          
   Component:  Vidalia      |     Version:          
  Resolution:               |    Keywords:          
      Parent:               |      Points:          
Actualpoints:               |  
----------------------------+-----------------------------------------------

Comment(by cypherpunks):

 Replying to [comment:16 mo]:
 > I still don't fully understand what you're after. There is a new alpha
 bundle, 2.4.10-alpha-2, that brings the same Tor Browser as 2.3.25-4. If
 you want to use other Tor versions for whatever reason, copy the tor.exe
 to "App" inside the bundle you want to use.
 >

 I want to run alpha Tor with TBB. How I do that is the open question. I
 prefer to install Tor, and run it from its install location with Vadalia.
 That is how I've done it for a long time up until now. The problem as you
 pointed out is SOCKS change. The most recent Tor alpha v0.2.4.1 hasn't yet
 been changed in its torrc. That's the problem, which I just figured out.

 The best fix is to wait for Tor devs to update Tor alpha torrc to 9150
 from 9050. Otherwise it's clunky to copy/paste tor.exe and I'm not so sure
 it's always going to be safe to do so (re breaking aspects of installed
 Tor vs. portable Tor). What I'll do until the Tor devs can update the Tor
 alpha torrc, is I'll manually edit the torrc in TBB from 9050 to 9150.

 > If you want to do more experiments, start over with newly extracted
 bundles. Looks like you did change stuff, otherwise there would not be any
 torrc.orig.1.
 >

 The torrc.orig.1 is created when you choose a different Tor via. Vadalia.
 If you use the Tor in TBB then there's only torrc, not torrc.orig.1.

 I always start with fresh bundles. There is a bug here, I just think
 you're not seeing it - the bug is Tor alpha default torrc hasn't been
 updated to reflect the updated SOCKS in TBB. I think it would be wise to
 use the same SOCKS for Tor and TBB, as Tor Project moves forward, rather
 than SOCKS 9050 for installed Tors and SOCKS 9150 for Tors found in TBB.


 > Your original report describes exactly this: Tor Browser is configured
 to use a different port than the tor.exe/torrc pair you point Vidalia at.
 Not a bug.

 I don't agree. We'll wait for others to chime in. See my comments above.
 This report has taken the long way to get to where it needs to go,
 granted, but there's is a bug here. See above.

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