Override geoip relay location with declared location

currently a relay stands in an other country than the server stands acutally in. The location information is wrong, because the IP-Space is registred in an other country. I could change the RIPE entry, but this makes maintaining the environment harder.

So, what about extending the config-file with a location flag and if the flag aint existing it uses the IP-lookup as backup solution.

changed milestone to %Tor: unspecified

added component::core tor/tor geoip milestone::Tor: unspecified needs-proposal priority::medium resolution::wontfix severity::normal status::closed tor-relay type::enhancement labels

One thing we can't do is to give nodes a wayto indicate their own country, and just believe it blindly. If we did that, then a hostile node could list any country that they want. For example, if a user has said "I don't want any nodes in the US!" we probably don't want nodes in the US to be able to say "Okay, I'm in Canada" and get believed blindly.

On the other hand, we could make that work by treating self-reported country as matching exclude lists and invalidating include lists, but not the other way round. IOW, if a node's detected country is cd and the reported country is cr, then:

• ExcludeNodes {cr} and ExcludeNodes {cd} would both exclude the node.
• Neither ExitNodes {cr} nor ExitNodes {cd} would include the node as an exit.

This sounds a bit tricky, and I'm not sure that it's 100% right or safe. More investigation needed.

Trac:
Milestone: N/A to Tor: 0.2.5.x-final
Keywords: N/A deleted, tor-client needs-proposal added

Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???
Summary: location of relay in config to Override geoip relay location with declared location

Yeah, I'm not sure this feature is worth the mess that it would bring.

Trac:
Sponsor: N/A to N/A
Severity: N/A to Normal

This is like #18005 (moved), but from the relay side rather than the client side.

The reality is that GeoIP is unrealiable: it is often based on the location of the company that controls the IP address, rather than actual geographical location of the server. And as IPv4 addresses become scarce, this will only get worse.

Also, there's no way for Tor to know whether the user wants geographical, legal, administrative, or some other boundary when they specify a country. Our current GeoIP files are a mix of all this.

I just can't see us fixing this with our current GeoIP data.

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: tor-client needs-proposal deleted, tor-client, tor-03-unspecified-201612, needs-proposal added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: tor-client deleted, geoip, tor-relay added
Resolution: N/A to wontfix
Status: new to closed
Reviewer: N/A to N/A

closed

moved to tpo/core/tor#10767 (closed)