[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #15846 [Metrics/CollecTor]: Publish (hashes of) historic Onionoo details documents (was: Sign responses)



#15846: Publish (hashes of) historic Onionoo details documents
-------------------------------+------------------------------
 Reporter:  karsten            |          Owner:  metrics-team
     Type:  enhancement        |         Status:  closed
 Priority:  Medium             |      Milestone:
Component:  Metrics/CollecTor  |        Version:
 Severity:  Normal             |     Resolution:  wontfix
 Keywords:  metrics-2017       |  Actual Points:
Parent ID:                     |         Points:
 Reviewer:                     |        Sponsor:
-------------------------------+------------------------------
Changes (by karsten):

 * status:  assigned => closed
 * resolution:   => wontfix
 * component:  Metrics/Onionoo => Metrics/CollecTor
 * severity:   => Normal


Comment:

 Updating the summary and component to reflect what this ticket is really
 about.

 However, I’m not convinced that we should create an archive of Onionoo
 responses. We already keep an archive of the underlying data, which is
 signed by the relays or directory authorities producing it. The suggested
 new archive would be mostly redundant, and in some cases it would even be
 worse: it would start whenever we start fetching Onionoo responses, and it
 would lack data whenever either Onionoo or the archiver (temporarily)
 breaks. We should instead work on including more history in Onionoo
 documents. If others want to create an archive of Onionoo responses,
 that‘s fine, but this is not something that we should be doing officially.

 Closing. Thanks for the suggestion anyway.

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