[metrics-team] onionoo exit_addresses semantics

[nusenu]

Hi,

due to dcf's idea I'm using onionoo data to detect rerouting exit relays 
(exits that do not really exit).

example (non-false positive):
https://lists.riseup.net/www/arc/ornetradar/2018-02/msg00056.html


I assume I stumbled on an issue with the exit_addresses data and would like
to hear your opinion. This is my assumption:

If an exit that does not actually have different inbout and output IPs,
but changes its ORPort IP address (example: dynamic IP), it will list its old IP as an exit_addresses after changing to a
new ORPort IP. Is that the case and if yes is that intended? 

Example:
D076C67EA072452C8F9A5C270224BDEFD910FAFD

OR IP address: 27.49.9.186 (relays_published: 2018-02-09 13:00)
Exit addresses lists the old IP:
**27.49.8.36** [...]

Descriptor published, OR IP, FP:

2018-02-08 18:40:13 27.49.8.36 D076C67EA072452C8F9A5C270224BDEFD910FAFD

Strictly speaking you could say that this does not violate the description of that field:

https://metrics.torproject.org/onionoo.html#details_relay_exit_addresses
> Array of IPv4 or IPv6 addresses that the relay used to exit to the
> Internet in the past 24 hours. IPv6 hex characters are all
> lower-case. Only those addresses are listed that are different from
> onion-routing addresses. Omitted if array is empty.

Depending on the interpretation of
"Only those addresses are listed that are different from
onion-routing addresses."

this is a potential bug or not.


-- 
https://mastodon.social/@nusenu
twitter: @nusenu_

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/metrics-team/attachments/20180209/96976dca/attachment.sig>