Opened 5 months ago

Last modified 4 months ago

#26051 assigned defect

please make it clear that exonerator has false-negatives

Reported by: cypherpunks Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/ExoneraTor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When ExoneraTor does not find an match it says:

"Result is negative"

We did not find IP address 1.2.3.4 on or within a day of 2018-01-01.

Please add a sentence that it is possible that there was an exit relay without Exonerator knowing about it (false-negatives).
Otherwise this could become a legal problem for the exit operator.

Child Tickets

Change History (3)

comment:1 Changed 4 months ago by karsten

Status: newneeds_information

Do you have a specific case in mind where ExoneraTor would not return an exit relay that was actually there? If so, we should try to fix that case. And if we can't for some reason, then we should consider making the message more defensive. Otherwise, I think we should leave the message unchanged.

Setting to needs_information with the intention to close in a week from now.

comment:2 Changed 4 months ago by cypherpunks

The following setups will cause a false-negative:

  • no IPv6 ORPort
  • IPv6 exiting allowed

or

  • IPv6 ORPort
  • OutboundBindAddressExit not in the same /48

(#16947)

comment:3 Changed 4 months ago by karsten

Status: needs_informationassigned

Alright, in that case we should add a specific message why results for IPv6 addresses might be less precise than one would expect. In theory, we'd only have to display that message when the user provides an IPv6 address.

Note: See TracTickets for help on using tickets.