Opened 7 years ago

Closed 4 years ago

#5927 closed defect (fixed)

GeoIP file doesn't get placed correctly

Reported by: bastik Owned by: erinn
Priority: Very High Milestone:
Component: Applications/Tor bundles/installation Version: Vidalia: 0.2.21
Severity: Keywords:
Cc: bastik, cccs1@…, barkerjr@… Actual Points:
Parent ID: #4347 Points:
Reviewer: Sponsor:

Description

I un-installed and removed anything related to the TorBundle and installed "vidalia-bridge-bundle-0.2.3.15-alpha-0.2.17.exe". One has to do this as admin.

Now the installer places the GeoIP file under "C:\Users\administrator\AppData\Local\Tor"

Launching Vidalia as admin gives the following warning.
"[Warning] Failed to open GEOIP file C:\Users\administrator\AppData\Roaming\tor\geoip. We've been configured to see which countries can access us as a bridge, and we need GEOIP information to tell which countries clients are in."

Previously I copied the GeoIP file from the admins Roaming\tor\ to the limited user Roaming\tor\ after every update. This time I copied it from "C:\Users\administrator\AppData\Local\Tor" to "C:\Users\[limited user]\AppData\Local\Tor", and the Warning appears there as well.

You place the file in \AppData\Roaming\tor\geoip, but look at AppData\Local\Tor

It's a fresh install, with default torrc and default vidalia.conf

Child Tickets

Change History (13)

comment:1 Changed 7 years ago by bastik

"You place the file in \AppData\Roaming\tor\geoip, but look at AppData\Local\Tor"

That's wrong. It's the opposite. The file is placed in "C:\Users\administrator\AppData\Local\Tor" and you look in "C:\Users\administrator\AppData\Roaming\tor\"

I'm sorry for the confusion this might added.

comment:2 Changed 7 years ago by arma

Parent ID: #4347

See #4347 for where we're working on this bug. Assuming it's the same bug.

comment:3 Changed 7 years ago by joecool

Cc: cccs1@… added
Priority: normalmajor
Version: Vidalia: 0.2.19

no this is a new bug:
"[Warning] Failed to open GEOIP file C:\Users\<USERNAME>\AppData\Roaming\tor\geoip. We've been configured to use (or avoid) nodes in certain countries, and we need GEOIP information to figure out which ones they are."

Apparently when moving stuff from Roaming Profile dir to Local Profile dir
"
0.2.16 11-Feb-2012

o Make the default data directory in windows be located in the Local

AppData instead of the Roaming one. Fixes bug 2319.

"
the default location in TOR (not Vidalia) wasn't changed OR the Bundle installer places stuff in wrong directory.

comment:4 Changed 7 years ago by joecool

A temporary fix would be adding this to torrc:
GeoIPFile C:/Users/<USERNAME>/AppData/Local/Tor/geoip

comment:5 Changed 6 years ago by arma

Is this still an issue?

I'm afraid we have no developers who are tracking this sort of thing. :( Somebody needs to identify which part of the bundle needs fixing, and exactly what the fix is.

comment:6 Changed 6 years ago by Tasaar

This is till an issue. No idea what part of the bundle needs fixing. Whatever part handles the GEOIP data I guess?

comment:7 Changed 6 years ago by bastik

Sorry for being silent. I install as admin and copy all needed files to the limited user account, for the geoip file (now files) I copied them to both locations. Also I did not use a vanilla torrc and/or vidalia.conf

Just updated to 2.4.10-alpha and this is still an issue. Installing as admin, replacing the config files and running as admin.

The installer places geoip files under
C:\Users\[$username]\AppData\Local\Tor

DataDirectory is
C:\Users\[$username]\AppData\Roaming\tor

Tor looks for the geoIP files in the DataDirectory.

I don't know what has to be changed; I remember a ticket saying that placing stuff under \Roaming\ is not a good idea. If it's known where to put the files, you can either change the default data directory or make the installer place them under the current default directory.

comment:8 Changed 6 years ago by bastik

#7956 is the ticket I was talking about.

BTW: I don't feel this as a child of #4347; here it's about where the file gets placed and where Tor looks for admins under Windows, while 4347 is for limited user accounts (where the file[s] do[es] not get placed at all)

comment:9 Changed 6 years ago by BarkerJr

Cc: barkerjr@… added

This is a bug in Tor, not Vidalia, right? The Version/Component might be wrong.

comment:10 Changed 6 years ago by AllHailDiscordia

Priority: majorcritical
Version: Vidalia: 0.2.19Vidalia: 0.2.21

This is still an issue with the latest Mac bundle (2.3.25, with Vidalia 0.2.21) - After installing and setting up a bridge, I saw the following warnings in the logs:

Aug 26 02:41:37.990 [Warning] Failed to open GEOIP file /builds/torbrowser-stable/build-scripts/build/i386/built/share/tor/geoip. We've been configured to see which countries can access us as a bridge, and we need GEOIP information to tell which countries clients are in.

I searched the drive and found the geoip file at /Applications/TorBrowser_en-US.app/Contents/Resources/Data/Tor/geoip, and when I updated my torrc as described above (by adding a GeoIPFile line to the torrc config from within Vidalia) it fixed things:

Aug 26 02:50:40.180 [Notice] Parsing GEOIP file /Applications/TorBrowser_en-US.app/Contents/Resources/Data/Tor/geoip.

Bumped priority to critical as it appears (based on the message) that it's a major problem for anyone trying to run a bridge out of the box (at least on Mac), and it should also be a relatively straightforward fix given that the real location of the geoip file is fixed/well-known for a standard Mac install.

comment:11 Changed 5 years ago by erinn

Keywords: needs-triage added

comment:12 Changed 5 years ago by erinn

Keywords: needs-triage removed

comment:13 Changed 4 years ago by cypherpunks

Resolution: fixed
Status: newclosed

Vidalia is deprecated, no Vidalia bundles anymore.

Note: See TracTickets for help on using tickets.