Opened 21 months ago

Closed 2 weeks ago

#26051 closed defect (duplicate)

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 (4)

comment:1 Changed 21 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 21 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 21 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.

comment:4 Changed 2 weeks ago by karsten

Resolution: duplicate
Status: assignedclosed

This issue is closely related to #31071. In fact, it should already be covered by that ticket.

As of now, we do not have any IPv6 addresses in exit lists, but when we have, we'll want to distinguish times when we did not have them from times when we did.

I'd rather resolve #31071 and include the IPv6 case there than add an informational message for IPv6 addresses being less precise that will become obsolete when exit lists contain IPv6 addresses.

Closing as duplicate.

Note: See TracTickets for help on using tickets.