Re: [tor-bugs] #28841 [Core Tor/Tor]: Write tool for onion service health assesment

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

#28841: Write tool for onion service health assesment
------------------------------------------+--------------------------------
 Reporter:  asn                           |          Owner:  (none)
     Type:  project                       |         Status:
                                          |  needs_information
 Priority:  Medium                        |      Milestone:  Tor:
                                          |  unspecified
Component:  Core Tor/Tor                  |        Version:
 Severity:  Normal                        |     Resolution:
 Keywords:  tor-hs reachability research  |  Actual Points:
Parent ID:                                |         Points:
 Reviewer:                                |        Sponsor:
------------------------------------------+--------------------------------
Changes (by rl1987):

 * status:  new => needs_information
 * type:  defect => project


Comment:

 Some questions/thoughts about this:

  1. There are two parts of Onion Service reachability: a) Ability of Tor
 network to communicate it's HSDesc reliably and do the
 introduction/rendezvous procedure when user tries to reach the Onion
 Service and b) Ability of server software at Onion Service side to
 properly listen for incoming connection and respond to requests. We care
 very much about the former, but do we care about the latter? I think not
 really, as that is responsibility of whoever is running Onion Service and
 they can use tools like Nagios to monitor things on their side. Also it is
 trivial to just `torify curl ...`. Any comments on this?
  2. Part a) from above can be further split into: a1) Ability of HSDirs to
 reliably inform user about the (latest) HSDesc and a2) Ability of Tor
 network to establish the final circuit between user and Onion Service. I
 suppose we want to measure both of these, and log some metrics about them?
 That would be timing information, as well success/failure for each try. We
 also want to detect cases of Tor network failing to perform any of the
 connection establishment steps.
  3. Do we want this to be based on stem? Can we currently do
 introduction/rendezvous stuff with Tor Control Port and get progress
 information that is fine-grained enough for this tool? Are there things we
 need to implement for Tor Control interface (beyond making `HSFETCH`
 support v3 descriptors) to make it ready?
  4. What would be the UI/API of such tool? Do we want JSON output for
 easier integration with other stuff? Do we want some API over HTTP?

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