Closed Bug 1529128 Opened 8 months ago Closed 7 months ago

Automatically update tracking protection lists when a new list-based feature is enabled

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox68 --- fixed

People

(Reporter: englehardt, Assigned: johannh)

References

(Blocks 1 open bug)

Details

(Whiteboard: [anti-tracking][privacytriage])

Attachments

(1 file)

We now consume different subsets of the tracking protection lists in different URL-classifier features. For example, the new fingerprinting blocking feature relies on base-fingerprinting-track-digest256, which isn't enabled by default. When a Nightly user enables the feature in about:preferences, Firefox will not have a copy of base-fingerprinting-track-digest256 and will not retrieve a copy until Firefox does one of its regular checks for list updates. I believe this currently happens once per hour.

This lag will make it appear to the user as if the new features aren't working. We've already had two cases of this confusion in our early testing. See Bug 1529116 and Bug 1527639.

Sounds like this should be done in the front-end code.

Whiteboard: [anti-tracking][privacytriage]

Can we get this into Firefox 67, for users and developers who are testing Fingerprinting and Cryptomining? This also is a frustrating gotcha during QA.

Priority: -- → P2
Target Milestone: --- → mozilla67
Assignee: nobody → jhofmann
Status: NEW → ASSIGNED
Priority: P2 → P1
Attachment #9050602 - Attachment description: Bug 1529128 - Automatically update cryptomingin and fingerprinting lists when the features are enabled. r=baku → Bug 1529128 - Automatically update cryptomining and fingerprinting lists when the features are enabled. r=baku
Pushed by jhofmann@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7896355d3f17
Automatically update cryptomining and fingerprinting lists when the features are enabled. r=baku
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.