Re: [tor-bugs] #16276 [Onionoo]: bug in onionoo's family set detection

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

#16276: bug in onionoo's family set detection
-----------------------------+-----------------
     Reporter:  cypherpunks  |      Owner:
         Type:  defect       |     Status:  new
     Priority:  major        |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by leeroy):

 Wait, doesn't (1) imply making the family key of the details document
 strictly effective family? Similarly, while (3) is simpler, it doesn't
 help an operator determine where there are problems. In comment:7,
 cypherpunks, mentions that (3) could be used by operators.

 It's not that I'm opposed to simplicity, it's that two explicit fields
 require computing the difference to check for problems (or do it
 manually). If (1) means strictly displaying effective family, it too
 doesn't make it easy to find problems. For the use-case described by
 cypherpunks, in comment:7, an operator who checks via Onionoo wouldn't be
 able to easily determine where the problems are. Thoughts?

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