Opened 5 years ago

Closed 23 months ago

#15323 closed defect (wontfix)

Investigate bug with sanitising of bridge reachability reports

Reported by: hellais Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Normal Keywords: archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


It appears that some bridge reachability reports that are using bridges taken from TBB are being hashed and the bridge_hash_fingeprint and bridge_address are not set.

We should investigate into either removing hashing for TBB reports (leaving the IP PORT in there since they are public) or if figure out why the above keys are not being set.

As an example here is a report that exhibits such problem:

We probably want to implement this while we are implementing:

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 23 months 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.