Atlas should explain how users can search for their bridge

There could be a link "how do I search for my bridge", or similar, that explains how to find their bridge's fingerprint and run it through SHA-1 before searching for it in Globe.

added component::metrics/relay search owner::irl priority::medium resolution::fixed severity::normal status::closed type::enhancement labels

Changing Globe tickets to be owned by isis.

Trac:
Status: new to assigned
Owner: rndm to isis

Trac:
Status: assigned to new

We're retiring Globe soon, but Atlas could also make use of some better documentation in this regard. Moving to the Atlas component.

Trac:
Severity: N/A to Normal
Reviewer: N/A to N/A
Component: Metrics/Globe to Metrics/Atlas
Owner: isis to phw
Sponsor: N/A to N/A

Trac:
Cc: N/A to irl@fsfe.org
Summary: Globe should explain how users can search for their bridge to Atlas should explain how users can search for their bridge

Trac:
Owner: phw to irl
Status: new to accepted

---

In order to avoid leaking bridge fingerprint and IP address information, this is obfuscated by the Onionoo service that Atlas uses to provide the relay and bridge data. In order to search for data about your bridge, you will need to search for the SHA1 hash of your bridge's identity fingerprint, not just the plain fingerprint.

On Linux and other Unix-like platforms, your fingerprint can often be found in /var/lib/tor/fingerprint. On some platforms it may be in a different location, but can also be found in your Tor log files.

If you're using a Linux or Unix-like system and your fingerprint is found in /var/lib/tor/fingerprint, you can use the following command to generate the SHA1 hash to search in Atlas:

# cat /var/lib/tor/fingerprint | sha1sum

or if you have extracted the fingerprint from your log files:

# echo -n "EXTRACTEDFINGERPRINT" | sha1sum

---

This is some draft text that I'm planning to integrate into the new help page coming out of #6787 (moved).

From IRC:

It should be:

cat /var/lib/tor/data/fingerprint | awk ' { print $2 } ' | sha1sum

Apparently that file contains both the nick and the fingerprint.

Nice and easy to review:

https://gitweb.torproject.org/user/irl/atlas.git/patch/?id=a357c473d27df6d3e2963d49b548761ea5671421

Trac:
Status: accepted to needs_review

Looks good to me! Thanks! :)

Trac:
Status: needs_review to merge_ready

Merged and deployed.

Trac:
Resolution: N/A to fixed
Status: merge_ready to closed

closed