[tor-bugs] #6798 [Tor bundles/installation]: Create Vidalia Obfsproxy Bridge Bundle containing Tor 0.2.4.2-alpha

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Mon Sep 17 20:44:47 UTC 2012


#6798: Create Vidalia Obfsproxy Bridge Bundle containing Tor 0.2.4.2-alpha
--------------------------------------+-------------------------------------
 Reporter:  karsten                   |          Owner:  erinn
     Type:  project                   |         Status:  new  
 Priority:  normal                    |      Milestone:       
Component:  Tor bundles/installation  |        Version:       
 Keywords:  SponsorG20120930          |         Parent:       
   Points:                            |   Actualpoints:       
--------------------------------------+-------------------------------------

Comment(by chiiph):

 Replying to [comment:8 erinn]:
 > I've made a preliminary bundle which almost works. It's here:
 >
 > https://people.torproject.org/~erinn/qa/alpha/vidalia-obfsproxy-bridge-
 bundle-0.2.4.2-alpha-0.3.3-alpha.exe
 >
 > a53967399d042a688466041875638bc89addf738c47b03b7432dc94446ec39f9
 vidalia-obfsproxy-bridge-bundle-0.2.4.2-alpha-0.3.3-alpha.exe
 >
 > The problem I'm having with it is that Vidalia claims it can't start
 Tor, but if you look at the message log Tor claims to have bootstrapped
 100%. Since Vidalia thinks it never initiates Tor, it doesn't seem to
 actually pay attention to its vidalia.conf settings (I think? still
 unclear on how Vidalia and Tor work together on Windows). So if you stop
 Tor, then go into settings, then set it as a bridge and start it again, it
 will actually start as a bridge... except over here, in the main Vidalia
 window, it only claims it connected to the Tor network successfully about
 50% of the time.
 >

 Does it say it couldn't start tor? or it couldn't connect to it? Because
 if you can see the log in the Message Log window as 100% bootstrapped and
 it says it wasn't able to start the tor process... well, it would be quite
 an interesting bug. If it says it cannot connect to it, then it's a
 configuration problem (and the content of the message log window is what
 it captures from stdout from the tor process).

 I'll test it and comment in here what I find out.

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


More information about the tor-bugs mailing list