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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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:             |
-----------------------+-------------------------

Comment (by starlight):

 Thank you for the update.

 Happy to learn the design is there already, I must have been looking at an
 old version of TorDNSEL or missed that both approaches are utilized.

 The Bywadu relay inspiring this ticket continued to exhibit the unlisted
 exit IP for something like two weeks after the scanner was restarted.
 Subsequently it was flagged as BadExit and then disappeared.  My guess
 from the BadExit marking is that this relay was gaming the exit scanner
 (reasons for the BadExit flag are not published).

 In the future when such relays appear they should be directly reported to
 the bad exit mailing list; I'll be certain to do that.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17297#comment:10>
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