[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33663 [Metrics/Exit Scanner]: Check checktest.py related errors shown by our network-health scanners
#33663: Check checktest.py related errors shown by our network-health scanners
-------------------------------------------------+-------------------------
Reporter: gk | Owner: gk
Type: task | Status:
| assigned
Priority: Medium | Milestone:
Component: Metrics/Exit Scanner | Version:
Severity: Normal | Resolution:
Keywords: network-health, network-health- | Actual Points:
roadmap-2020Q1, GeorgKoppen202003 |
Parent ID: #33180 | Points: 0.5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by gk):
* component: Metrics/Consensus Health => Metrics/Exit Scanner
Comment:
If I look at the exit-lists data, say, from 3/23/2020 I can see something
like:
{{{
2020-03-23-04-02-00:ExitNode 296B2178FD742AB35AB20C9ADF04D5DFD3D407EB
2020-03-23-04-02-00-Published 2020-03-22 21:30:04
2020-03-23-04-02-00-LastStatus 2020-03-23 02:00:00
2020-03-23-04-02-00-ExitAddress 206.55.74.0 2020-03-23 02:32:12
}}}
That holds for all the 24 measurements on that day. So, it seems the exit
scanner thinks on one hand that this relay is indeed an exit but when
asked via `exitmap`'s `checktest` module (that is querying
`https://check.torproject.org/api/ip`) one gets an `"IsTor":false` back.
Sounds like a check bug worth investigating.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33663#comment:4>
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