Opened 9 years ago

Closed 9 years ago

#2066 closed defect (invalid)

no country flags/City-Country id on nodes in Tor Network Map

Reported by: TorUser Owned by:
Priority: Very High Milestone:
Component: Archived/Vidalia Version: Tor: 0.2.1.26
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Recently the country flags and City-Country names disappeared in the Tor Network Map display page of Vidalia. I suspect a problem connected to the error message now appearing on the Message Log page.

error message is;
Oct 13 23:01:58.631 [Notice] Have tried resolving or connecting to address 'geoips.vidalia-project.net' at 3 different places. Giving up.
Oct 13 23:05:36.584 [Notice] Have tried resolving or connecting to address 'geoips.vidalia-project.net' at 3 different places. Giving up.
Oct 13 23:06:11.866 [Notice] Have tried resolving or connecting to address 'geoips.vidalia-project.net' at 3 different places. Giving up.
Oct 13 23:06:46.725 [Notice] Have tried resolving or connecting to address 'geoips.vidalia-project.net' at 3 different places. Giving up.
Oct 13 23:07:48.241 [Notice] Have tried resolving or connecting to address 'geoips.vidalia-project.net' at 3 different places. Giving up.

this message repeated many times in error log.

I suspect that this will break the ExcludeNodes, ExcludeExitNodes, EntryNodes, ExitNodes clauses in torrc file if you are using country codes to include/exclude nodes. For some users this may cause serious security problems or tracabilty problem because of connections made to hostile countrys (police, military etc).

Is there a workaround or fix for this problem? or is this even a problem to worry about?

I have verified this to exist on several different computers, most running Win XP Home Sp4/Tor 0.2.1.26 or Win XP Pro Sp3/Tor 0.2.1.26
one Win Vista Sp1/Tor 0.2.1.26 all have latest Msoft updates and no firewalls blocking access to tor nodes.

Child Tickets

Change History (1)

comment:1 Changed 9 years ago by Sebastian

Resolution: invalid
Status: newclosed

This is a Vidalia problem that is solved by updating to 0.2.10. Tor's exclude/entry/whatevernodes options are unaffected.

Note: See TracTickets for help on using tickets.