Closed Bug 1546906 Opened 5 months ago Closed 5 months ago

Consider changing TrackingClassification fingerprinting checking list from base to strict

Categories

(Core :: Networking, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: xeonchen, Assigned: xeonchen)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

Currently the checking stategy is CLASSIFIED_FINGERPRINTING, and according to offiline discussion with :tanvi, we're going to change it to CLASSIFIED_FINGERPRINTING_CONTENT.

[1] https://searchfox.org/mozilla-central/rev/d143f8ce30d1bcfee7a1227c27bf876a85f8cede/netwerk/protocol/http/nsHttpChannel.cpp#1346

Hi Tanvi,

My current experiment is based on setting

urlclassifier.features.fingerprinting.annotate.blacklistTables to
base-fingerprinting-track-digest256,

which is CLASSIFIED_FINGERPRINTING list.

I'm not sure the list we're going to use, but if base-fingerprinting-track-digest256 is used, then we probably won't have any probe falls into fingerprinting categories.

Would you confirm we'd like to adopt this change?

Flags: needinfo?(tanvi)
No longer blocks: fpcmblocking
Pushed by xeonchen@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/409bdbc32737
use strict fingerprint category for telemetry; r=dragana,tanvi
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68

Talked to Gary and confirmed with him to use the strict list for fingerprinting category. Fingerprinters on the basic list will fall into the tracker classifications.

Flags: needinfo?(tanvi)
You need to log in before you can comment on or make changes to this bug.