Make cryptomining and fingerprinting annotations use the "strict" list always

RESOLVED FIXED in Firefox 68

Status

()

enhancement
RESOLVED FIXED
3 months ago
3 months ago

People

(Reporter: englehardt, Assigned: baku)

Tracking

(Blocks 1 bug)

unspecified
mozilla68
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox68 fixed)

Details

Attachments

(1 attachment, 1 obsolete attachment)

In Bug 1533074 we landed cryptomining-annotation and fingerprinting-annotation. These currently use the base- versions of the cryptomining and fingerprinting lists. In Bug 1536488 we moved the tracking-annotation feature over to always use the strict list. Since both the cryptomining and fingerprinting lists also have a base- and content- version of the lists [0] we should do the same for these annotations.

[0] https://wiki.mozilla.org/Security/Tracking_protection#Lists

Assignee

Updated

3 months ago
Assignee: nobody → amarchesini
Reporter

Comment 1

3 months ago

One relevant thing to highlight here. The fingerprinting list is not a strict subset of the tracking list -- as in, some fingerprinters are not considered trackers. From [0]:

  • base-fingerprinting-track-digest256: domains in both the Fingerprinting category AND in one of the tracking categories (Advertising, Analytics, Social, or Content)
  • content-fingerprinting-track-digest256: domains in the Fingerprinting category that are NOT in one of the tracking categories

This might impact how we build CLASSIFIED_TRACKING.

Comment 3

3 months ago
Pushed by amarchesini@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a247a37c1e9b
Make cryptomining and fingerprinting annotations use the "strict" list always, r=dimi

Comment 4

3 months ago

Test patch to verify correct MC settings. Reference bug is a CLOSED, NOFIX.

Attachment #9055723 - Attachment is obsolete: true

Comment 5

3 months ago
bugherder
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.