[tor-bugs] #17297 [Tor Check]: TorCheck fails on new exit egress IP not in exit DB, confusing to users

[Tor Bug Tracker & Wiki]

#17297: TorCheck fails on new exit egress IP not in exit DB, confusing to users
---------------------------+---------------------
     Reporter:  starlight  |      Owner:  arlolra
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:
    Component:  Tor Check  |    Version:
   Resolution:             |   Keywords:
Actual Points:             |  Parent ID:
       Points:             |    Sponsor:
---------------------------+---------------------
Changes (by s7r):

 * cc: karsten (added)


Comment:

 Let's figure out if this is a bug first.

 It could be only a limitation of the exit-list, since the only way we can
 truly discover all the exit IP addresses is to exit via each and every
 exit relay. But even so, some relays have more than 1 exit IP address,
 some might change their exit IP address on the fly or after we check it,
 some could use VPNs / proxies for certain routes, etc. so the exit list
 will never be 100% accurate.

 I have an example that it works sometimes (or probably most of the times):

 Check for example:
 PrivacyRepublic0001 178.32.181.96
 PrivacyRepublic0002 178.32.181.97
 Both exit with IP: 37.187.129.166

 It actually works very good, when you connect to check.torproject.org
 it says OK > you are using Tor.

 Also, Exonerator (onionoo) knows how to handle it too:
 https://exonerator.torproject.org/?ip=37.187.129.166&timestamp=2015-10-10

 It will even return the correct results on atlas:
 https://atlas.torproject.org/#search/37.187.129.166

 CC'ing Karsten as this is somehow onionoo related.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17297#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online