[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6266 [Tor Client]: maxmind geoip db is starting to label Tor relays as country "A1"
#6266: maxmind geoip db is starting to label Tor relays as country "A1"
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor Client | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by karsten):
> The more A1 relays we have, the more useless it is to think settings
> EntryNodes or ExitNodes by country works. Especially for people who are
> trying to Exclude countries.
True. The June database contains 341 "A1" entries, compared to 96 such
entries in April and May and even fewer before. We'll have to do
something about that.
> So the first question is, are the Tor relays that they're adding only
> single IP blocks?
I looked up all relays in the consensus from 2012-07-01 00:00:00 UTC in
the June database. Here are the matches:
{{{
from_addr,to_addr,country num_addr relay_addr
773032192,773032447,A1 256 46.19.137.238
782665472,782666751,A1 1280 46.166.135.90
1249381764,1249381764,A1 1 74.120.13.132
1308079522,1308079525,A1 4 77.247.181.162
1308079522,1308079525,A1 4 77.247.181.163
1308079522,1308079525,A1 4 77.247.181.164
1308079522,1308079525,A1 4 77.247.181.165
1357767240,1357769287,A1 2048 80.237.226.73
1357767240,1357769287,A1 2048 80.237.226.74
1357767240,1357769287,A1 2048 80.237.226.75
1357767240,1357769287,A1 2048 80.237.226.76
1388570842,1388570842,A1 1 82.195.232.218
1839458760,1839458760,A1 1 109.163.233.200
1999278098,1999278098,A1 1 119.42.144.18
2302190382,2302190382,A1 1 137.56.163.46
2461603763,2461603763,A1 1 146.185.23.179
2919159874,2919159877,A1 4 173.254.216.66
2919159874,2919159877,A1 4 173.254.216.67
2919159874,2919159877,A1 4 173.254.216.68
2919159874,2919159877,A1 4 173.254.216.69
2987528448,2987528703,A1 256 178.18.17.111
2988550435,2988550435,A1 1 178.33.169.35
2991183872,2991185919,A1 2048 178.73.216.197
3341849376,3341853471,A1 4096 199.48.147.35
3341849376,3341853471,A1 4096 199.48.147.36
3341849376,3341853471,A1 4096 199.48.147.37
3341849376,3341853471,A1 4096 199.48.147.38
3341849376,3341853471,A1 4096 199.48.147.39
3341849376,3341853471,A1 4096 199.48.147.40
3341849376,3341853471,A1 4096 199.48.147.41
3392946720,3392946720,A1 1 202.60.66.32
3584245803,3584245803,A1 1 213.163.64.43
3584246066,3584246066,A1 1 213.163.65.50
}}}
The 12 ranges covering 4 addresses or less look like we could repair them
by merging them with the previous and/or next range. The 6 ranges with
more than 4 addresses might be more difficult, at least without using
additional information.
What we could also do is look up the "A1" ranges in a second GeoIP
database and use those entries. We'd have to do it in a way that is
easily reproducible for others.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6266#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs