Closed Bug 1594994 Opened 5 years ago Closed 5 years ago

While using Debugging Tool, We observed browser is not blocking third-party cookies for a tracker explicitly mentioned by user in "about:config" list

Categories

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

70 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1501461

People

(Reporter: beingshobhit, Assigned: dimi)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

I went into about:config of Mozilla to explicitly mention "disqus.com" as a tracker.
Then I somehow visited www.etherscan.io, and clicked on Disqus comments present in the bottom of the page.

Actual results:

Then, I inspected the page, went into Network Request header, and found that there is a Content Blocking Shield next to disqus.com, but cookies are still sent to "disqus.com" by the browser.

Expected results:

We have clearly marked "Disqus.com" as a tracker. So, if any third-party component is a tracker, Mozilla must restrict sending cookies to that tracker. Thus, here "disqus.com" should have not received the cookies from browser.

Flags: needinfo?(tgrabowski)

(In reply to beingshobhit from comment #0)

I went into about:config of Mozilla to explicitly mention "disqus.com" as a tracker.

Using which preference?

Group: firefox-core-security
Component: Untriaged → Privacy: Anti-Tracking
Flags: needinfo?(beingshobhit)
Product: Firefox → Core

I used 'Strict Protection' preference.

Flags: needinfo?(beingshobhit)

(In reply to beingshobhit from comment #2)

I used 'Strict Protection' preference.

My question was how/where you added disqus.com in about:config.

Flags: needinfo?(beingshobhit)

I added a preference name "urlclassifier.trackingAnnotationTable.testEntries" in about:config , and set its string value to "disqus.com".

Flags: needinfo?(beingshobhit)

Hopefully Ehsan can explain what TP is and is not supposed to do based on that pref.

Flags: needinfo?(tgrabowski) → needinfo?(ehsan)

If you're curious to know exactly what's going on behind the scenes, you can turn on the relevant logs using the following environment variables: MOZ_LOG=nsChannelClassifier:5,AntiTracking:5 MOZ_LOG_FILE=log-file, but the urlclassifier.trackingAnnotationTable.testEntries preference isn't intended for users to edit (which is why it's a hidden preference.) FWIW this pref isn't really tested and using it some things may not work very well, so be warned if you're going to explore this path. :-)

Probably more relevant to your question, disqus.com is on the "Level 2" Disconnect block list which isn't yet turned on in ETP by default yet. You can use the privacy.annotate_channels.strict_list.enabled pref to turn it on manually if you'd like to test how things would look like when Firefox blocks cookies/storage from disqus.com. We're tracking the work to enable this preference for all users over in bug 1501461. I think this bug is probably a duplicate of bug 1501461...

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(ehsan)
Resolution: --- → DUPLICATE

(In reply to :ehsan akhgari from comment #6)

If you're curious to know exactly what's going on behind the scenes, you can turn on the relevant logs using the following environment variables: MOZ_LOG=nsChannelClassifier:5,AntiTracking:5 MOZ_LOG_FILE=log-file, but the urlclassifier.trackingAnnotationTable.testEntries preference isn't intended for users to edit (which is why it's a hidden preference.) FWIW this pref isn't really tested and using it some things may not work very well, so be warned if you're going to explore this path. :-)

BTW as I have mentioned in bug 1589407 comment 0, I highly suspect that this preference is currently not functioning correctly...

I thought that "urlclassifier.trackingAnnotationTable.testEntries" didn't work in some cases, but I tested the pref, The pref works on both release build and nightly build. As ehsan pointed out, this is a duplicate of bug 1501461.

Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.