[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21615 [Metrics/Atlas]: Use hashed fingerprint in all lookups
#21615: Use hashed fingerprint in all lookups
---------------------------+-----------------------------------
Reporter: cypherpunks | Owner: irl
Type: enhancement | Status: needs_information
Priority: Medium | Milestone:
Component: Metrics/Atlas | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------+-----------------------------------
Comment (by cypherpunks):
Thanks for the detailed explanation. This means that any fingerprint we
get back from Onionoo (being either `R` or `H(B)`) we can safely rehash.
And because we expect users to give us either `R` or `H(B)` too we can
also safely rehash those. This is the current situation.
The problem is with the detailed lookups performed by the search page
which uses whatever Onionoo returns and thus sends requests using `R` and
`H(B)` directly. FWICT this is the only edge case where there's no
rehashing.
The solution would be to let the relay model on the Atlas side always hash
whatever fingerprint is assigned to it when it's created and store it in a
separate field. Then we would have one field which contains either `R` or
`H(B)` for showing on the details page and one field which contains `H(R)`
or `H(H(B))` for making subsequent requests (such as bandwidth, weights,
etc).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21615#comment:7>
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