[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33663 [Metrics/Consensus Health]: 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/Consensus Health | Version:
Severity: Normal | Resolution:
Keywords: network-health, network-health- | Actual Points:
roadmap-2020Q1, GeorgKoppen202003 |
Parent ID: #33180 | Points: 0.5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by gk):
The exit policy of that relay is sufficiently broken that it should not be
used as exit (I pinged the operator and will badexit the relay early next
week if I don't hear back), however it's not clear yet why check actually
thinks it's the case.
[https://github.com/NullHypothesis/exitmap/blob/master/src/modules/checktest.py
`checktest.py`] is pretty close to what `exitscanner`
[https://gitweb.torproject.org/metrics-cloud.git/tree/ansible/roles/exit-
scanner/files/ipscan.py is using]. However, as the error message in the
description clearly shows the exit *is* able to resolve
`check.torproject.org` (thus, the exit policy is acceptable for that
particular test at least. Or maybe that's only holding for most of the
cases when `check.torproject.org` resolves to `116.202.120.181`?). Thus,
it is not obvious where the `"IsTor":false` is coming from.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33663#comment:1>
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