#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 teor): Replying to [comment:21 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 am a human who regularly uses CollecTor via the web interface (not stem or metrics-lib). But if someone wrote a nice easy program or web interface for me to get a bandwidth file from a vote, I would use that instead. Replying to [comment:22 juga]: > Following #26698, last changes are in https://github.com/torproject/tor/pull/492, which is putting a sha1-digest (hex-encoded) We do not use broken hash algorithms in new code. Replying to [comment:25 irl]: > I think that a base64-encoded SHA256 digest of the file would be the thing to have. Ok. If we need to discuss the hash any more, let's do it on the hash ticket #26698. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21378#comment:26> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs