Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#6139 closed enhancement (implemented)

Update to June GeoIP database

Reported by: karsten Owned by:
Priority: Medium Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

See branch geoip-june2012 in my public repository.

I manually removed range 0.116.0.0 to 0.119.255.255 which Maxmind says is assigned to AT. This is very likely a bug in their database, because 0.0.0.0/8 is a reserved range. I sent an update request to Maxmind, but didn't hear back from them. I stated in the commit message that I manually removed that line from our geoip file.

I based this branch on maint-0.2.2. Is this still the right thing to do, or should I base future branches on master or something else?

Child Tickets

Change History (4)

comment:1 Changed 8 years ago by karsten

Status: newneeds_review

comment:2 Changed 8 years ago by arma

Resolution: implemented
Status: needs_reviewclosed

I think putting it in maint-0.2.2 is still appropriate for now. The main risk is that the monthly geoip update introduces a mistake that actually affects users (like placing Noisebridge in Syria).

comment:3 Changed 7 years ago by nickm

Keywords: tor-client added

comment:4 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.