[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:  closed
 Priority:  High       |      Milestone:
Component:  Tor Check  |        Version:
 Severity:  Normal     |     Resolution:  fixed
 Keywords:             |  Actual Points:
Parent ID:             |         Points:
  Sponsor:             |
-----------------------+-------------------------
Changes (by arlolra):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Thanks for reporting and sorry for being slow.

 Pretty sure this particular instance was the result of TorDNSEL's tor
 process being killed, as suggested by karsten in #comment:4.

 > They rely on published exit policies to determine exit IP addresses.

 No, TorDNSEL takes the same approach as the alternative you linked to,
 [https://github.com/NullHypothesis/exitmap exitmap].

 From the project description,

 > Previous DNSELs scraped Tor's network directory for exit node IP
 addresses, but this method fails to list nodes that don't advertise their
 exit address in the directory. TorDNSEL actively tests through these nodes
 to provide a more accurate list.

 See https://www.torproject.org/projects/tordnsel.html.en

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