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

Re: [tor-bugs] #21378 [Metrics/CollecTor]: Archive bwauth bandwidth files

#21378: Archive bwauth bandwidth files
------------------------------------+------------------------------
 Reporter:  tom                     |          Owner:  metrics-team
     Type:  enhancement             |         Status:  new
 Priority:  Medium                  |      Milestone:
Component:  Metrics/CollecTor       |        Version:
 Severity:  Normal                  |     Resolution:
 Keywords:  tor-bwauth tor-dirauth  |  Actual Points:
Parent ID:                          |         Points:
 Reviewer:                          |        Sponsor:
------------------------------------+------------------------------

Comment (by irl):

 I've already started work on a prototype Python version of this CollecTor
 module. Can we use the same encoding for the digest that is used to
 reference vote, server descriptor or extra info descriptor digests? This
 will allow for better code reuse. We will convert things into whatever at
 the point they are read into CollecTor and convert them back when read
 out. Consistency within the spec is more important than consistency with
 code that I'm currently replacing.

 Humans using CollecTor will typically use either stem or metrics-lib to
 interact with it. I'm also playing with the idea that CollecTor will
 itself implement a dir-spec server and pretend to be a directory cache
 that also serves historical descriptors. We might still have legacy things
 internally that we need to make conversions for but these should be things
 that we can eventually get rid of, not have to keep forever because that's
 how the spec is written.

 This means that ideally, we would have hex encoded SHA1 and/or base64
 encoded SHA256. (At least, in my opinion, I'm happy to hear counter
 arguments. Maybe I've not understood something.)

 {{{
        "sha1-digest" is a hex-encoded digest (using upper-case characters)
 of
        the router's extra-info document, as signed in the router's extra-
 info
        (that is, not including the signature).  (If this field is absent,
 the
        router is not uploading a corresponding extra-info document.)

        "sha256-digest" is a base64-encoded SHA256 digest of the extra-info
        document, computed over the same data.
 }}}

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