Re: [tor-bugs] #33663 [Metrics/Consensus Health]: Check checktest.py related errors shown by our network-health scanners

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33663 [Metrics/Consensus Health]: Check checktest.py related errors shown by our network-health scanners

[Tor Bug Tracker & Wiki]

#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 irl):

 The issue is not whether the exit is able to resolve it, but whether the
 exit is able to exit to it. Exits need to be able to make exit connections
 to 116.202.120.181:443. This is a fundamental limitation of the current
 exit scanner and would need redesign to do differently.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33663 [Metrics/Consensus Health]: Check checktest.py related errors shown by our network-health scanners

[Tor Bug Tracker & Wiki]

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

 Replying to [comment:2 irl]:
 > The issue is not whether the exit is able to resolve it, but whether the
 exit is able to exit to it. Exits need to be able to make exit connections
 to 116.202.120.181:443. This is a fundamental limitation of the current
 exit scanner and would need redesign to do differently.

 Thanks, yes, being able to resolve `check.torproject.org` is just a
 necessary requirement but not sufficient. I should have been clearer,
 sorry for that. So, the node can make an exit connection to
 `check.torproject.org` as it gets JSON back and complaining afterwards
 that it got `"IsTor":false`. Now, there are cases where this can happen,
 e.g. as the exitscanner might have a different consensus containing relays
 the check test script does not have once it is run and vice versa but
 that's usually not causing a permanent failure as in this case.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs