Opened 6 years ago

Closed 2 years ago

#15647 closed enhancement (wontfix)

ooni-probe's bridge_reachability tests should require bridge fingerprints for the inputs

Reported by: isis Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Normal Keywords: ooni-probe, bridge-reachability, dataviz, archived-closed-2018-07-04
Cc: isis, hellais, aagbsn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Requiring the input to have bridge fingerprints would help to partially fix issues like, and it would help to solve the problem where people doing data visualisation on the bridge_reachability report data are forced to display data for a bridge based on its IP:port (because no fingerprint, and thus no hashed fingerprint, is available). For example, this is currently the case for some of the bridges on

In fact, perhaps the sanitised reports should only contain the hashed fingerprint, neither the fingerprints nor the addresses? (Following the principle of avoiding handing others a loaded gun with the safety off.) (Although perhaps this should be another ticket.)

Child Tickets

Change History (2)

comment:1 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 2 years ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.