Opened 5 years ago

Closed 9 months ago

#9935 closed defect (wontfix)

Vidalia trashes 'tor' different host config if 'vidalia.conf' not preserved in TBB update

Reported by: starlight Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version:
Severity: Normal Keywords: archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If one configures 'tor' on a different host but
uses TBB+Vidalia to monitor 'tor' and browse,
forgetting to preserve the 'vidalia.conf' file
when updating TBB results in Vidalia trashing
the 'tor' relay configuration. Thankfully
I had a backup.

Vidalia should first attempt to download the
existing config when the IP of an remote
system 'tor' is entered.

This is true for

tor-browser-gnu-linux-x86_64-2.3.25-13-dev-en-US

and

tor-browser-gnu-linux-x86_64-2.4.17-beta-2-dev-en-US

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by starlight

This functionality may already be partially in place.

Found that removing the "Changed" lines from
'vidalia.conf' after restoring 'torrc' and
restarting 'tor' and Vidalia resulted in
Vidalia importing settings rather than
attempting to overwrite them again.

comment:2 Changed 5 years ago by arma

Vidalia is deprecated and TBB 3.0 doesn't include it:
https://blog.torproject.org/category/tags/tbb-30

You should operate under the assumption that Vidalia will get zero patches from here on out (as has been the case for the past year or more).

Does that mean we should close this ticket, or is there an issue with tbb3.0 also?

comment:3 Changed 16 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:4 Changed 9 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.