#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 irl): Ok, I see the inconsistency now. The search page, when fetching the details documents, isn't hashing but the details page is regardless of whether or not the fingerprint has already been hashed. So, to add to the examples of what is happening, I have two bridges that with the following search will do lookups for details documents of the hashed fingerprint but when going to the details pages, the hashed fingerprint will be hashed once more. https://atlas.torproject.org/#search/irlDn42 The hashed fingerprints are already leaked in the search step, so either this is a defect in that we're leaking hashed fingerprints that need to be hashed again or there is an enhancement to be had in removing the re- hashing when fetching the details documents for the details pages. Currently, by the time we get to the details pages we've already leaked the hashed fingerprint for the bridge. karsten: I guess the question is, how many times do we need to hash the fingerprint? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21615#comment:5> 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