[tor-bugs] #2905 [Vidalia]: Adapt Vidalia UI to allow users to avoid connecting to the public tor network

[Tor Bug Tracker & Wiki]

#2905: Adapt Vidalia UI to allow users to avoid connecting to the public tor
network
---------------------+------------------------------------------------------
 Reporter:  anonym   |          Owner:  chiiph         
     Type:  defect   |         Status:  new            
 Priority:  major    |      Milestone:  Vidalia: 0.2.13
Component:  Vidalia  |        Version:  Vidalia 0.2.10 
 Keywords:  bridges  |         Parent:                 
   Points:           |   Actualpoints:                 
---------------------+------------------------------------------------------

Comment(by anonym):

 Replying to [comment:11 chiiph]:
 > Anyway, I think I've gotten derailed here :) but what I mean is that we
 have to find a middle point, no solution will be perfect.

 I think you're right. Let's start anew and let me put it this way instead.
 What's the problem of having the following behaviour instead:

 If "My ISP blocks..." is checked but no bridges are configured, then set
 UseBridges=1 and let Tor be unable to connect. The current prompt you
 added is changed to a yes/no-prompt that says:

   Tor is currently configured to only allow connections through bridges,
 but no bridges are configured. With this configuration Tor will need at
 least one working bridge configured in order to work. Do you want to open
 the network settings to resolve this issue?

 W.r.t. buttons, "yes" opens the bridge settings, "no" does nothing, so Tor
 remains unable to connect.

 The only problem I can think of is with backwards compatibility: a user
 that checked the "My ISP blocks..." box without adding any bridge in a
 previous vidalia version would suddenly have a non-working Tor thanks to
 the stuff in vidalia.conf that worked previously. Because of this it may
 be better to show the prompt whenever settings are applied (i.e.
 ConfigDialog::applyChanges()) since that would show it in all these cases:

  * when the user presses save in the settings
  * when vidalia imports settings from a running Tor instance
  * when loading vidalia.conf (which would give a pointer to the user
 experiencing this backwards compatibility problem)

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