Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#7877 closed enhancement (duplicate)

Web interface for looking up bridge status?

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: karsten, isis Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We keep and publish scrubbed bridge descriptors -- hashing the IP address, fingerprint, etc -- as well as bridge pool assignments:
https://metrics.torproject.org/data.html#bridgedesc
https://metrics.torproject.org/formats.html#bridgepool

The process of looking up whether your bridge is working means you need to do a sha1 of your fingerprint. That means most bridge operators won't do it.

To make it easier, we should offer a web interface where you tell it your fingerprint, and it tells you the corresponding bridge descriptor (including extrainfo details).

(In my ideal world, users could just query Tonga directly, which would mean much more up-to-date answers here. But Tonga quite rightly doesn't answer bridge questions over its unencrypted dirport, and browsers quite rightly don't know how to encapsulate their http queries in the Tor protocol. So I guess that direction is a dead-end.)

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by arma

Cc: karsten added

comment:2 Changed 7 years ago by karsten

Resolution: duplicate
Status: newclosed

Atlas/Onionoo are actually quite close to what you describe. The missing piece is that Atlas takes a 40-character hex input, applies SHA-1 on it using JavaScript, sends the result to Onionoo, and displays the obtained bridge details. That is described in #6320, which is why I'm closing this ticket as duplicate. Please add more thoughts to that ticket, or re-open this ticket if you meant something else.

What we should avoid, if we can, is sending an unhashed bridge fingerprint to Onionoo. While this isn't as problematic on yatei (because it enforces https and strips parameters from sanitized web logs), it's going to be problematic as soon as people use other Onionoo instances than the "official" one. It's best if Onionoo doesn't learn unhashed bridge fingerprints in the first place. The Atlas/Onionoo solution in #6320 doesn't have this problem.

Querying Tonga directly does indeed look like a dead end: this doesn't give us bridge pool assignment information; querying Tonga means putting even more load on it. We can probably come up with more problems the longer we think about it.

comment:3 Changed 5 years ago by isis

Cc: isis added

comment:4 in reply to:  3 Changed 5 years ago by karsten

Replying to isis:

Hmm? Nothing to see here, move along.

Note: See TracTickets for help on using tickets.