Allow resource status lookup by hashed fingerprint
Rdsys's resource status page requires a bridge's fingerprint to look up its status. The page should also accept the bridge's hashed fingerprint, like Relay Search.
Activity
changed milestone to %Sponsor 30 - Objective 2.3
added Sponsor 30 - FINISHED label
mentioned in issue tpo/core/tor#30477 (closed)
closed with commit c01d391d
Quoting the patch's commit message:
A bridge's fingerprint is confidential information because one can use it to fetch the bridge's descriptor (which includes its address) from Serge. We should therefore support status lookups based on hashed fingerprints, similar to how Relay Search does it. That allows bridge operators to publish their bridge's status page URL.
This patch makes it possible to look up a bridge's status based on fingerprint or hashed fingerprint. The patch also makes the lookup slightly more robust by removing leading and trailing spaces, and by ignoring the capitalisation of the given fingerprint.
To get this done, the patch had to change the way we determine a bridge's Uid -- it's now based on hashed fingerprints rather than fingerprints.