[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17297 [Tor Check]: TorCheck fails on new exit egress IP not in exit DB, confusing to users
#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 arlolra):
> 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).
It got BadExit'd with #17303. The redirection described there may in fact
be the real reason why TorDNSEL was never able to resolve the correct IP
for that node.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17297#comment:11>
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