Project

General

Profile

Feature #7614

Feature #5840: Do not restart Vidalia on network reconnect

Have Vidalia automatically (re-)connect to a Tor instance started after startup

Added by intrigeri over 5 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Tor configuration
Target version:
-
Start date:
07/19/2014
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Yes
Affected tool:

Description

See the parent ticket for the rationale, and the upstream ticket for details.

Vidalia is unmaintained upstream these days, so there's little chance that this bug is magically fixed there if we don't do it ourselves. In case it matters, we only care about the case when Vidalia is talking to Tor via a ControlSocket.

Vidalia is written in C++/Qt. The code lives in https://git-tails.immerda.ch/vidalia.

History

#1 Updated by BitingBird about 5 years ago

We're planning on removing Vidalia, so I think this should be rejected (better to work on the replacement).

#2 Updated by intrigeri almost 5 years ago

  • Affected tool set to Vidalia

#3 Updated by intrigeri almost 5 years ago

  • Priority changed from Normal to Low

Can still be useful if we get a good patch in time for 1.4, otherwise should be rejected IMO, depending on the progress on the Tor Monitor front.

#4 Updated by BitingBird over 4 years ago

  • Status changed from Confirmed to Rejected

Vidalia will be replaced by TorMonitor -> let's not work on that anymore :)

#5 Updated by intrigeri over 3 years ago

  • Affected tool deleted (Vidalia)

Also available in: Atom PDF