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

Status: RESOLVED FIXED

(Core :: Privacy: Anti-Tracking, enhancement)

Description

[Steven Englehardt [:englehardt]]

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

Comment 1

[Steven Englehardt [:englehardt]]

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 2

[Andrea Marchesini [:baku]]

Attachment: Bug 1539637 - Make cryptomining and fingerprinting annotations use the "strict" list always, r?dimi

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a247a37c1e9b
Make cryptomining and fingerprinting annotations use the "strict" list always, r=dimi

Comment 4

[Alex R.]

Attachment: Bug N/A - testing patch attempt 1, please ignore r=davidwalsh

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

Comment 5

[Arthur Iakab [arthur_iakab]]

https://hg.mozilla.org/mozilla-central/rev/a247a37c1e9b