Review Mozilla 1832791: Implement a Remote Settings for the Quarantined Domains pref

Link: https://bugzilla.mozilla.org/show_bug.cgi?id=1832791

More remote setting to potentially purge for Mullvad Browser and maybe Tor Browser.

added 13.0 stable Code Audit Linkability FF115-esr labels

assigned to @pierov

marked this issue as related to tor-browser-spec#40062 (closed)

see #41825 (closed)

added Next label

added Task label

added All Platforms label

mentioned in issue #41825 (closed)

marked #41825 (closed) as a duplicate of this issue

marked this issue as related to #41825 (closed)

From #41825 (closed):

sumo article - https://support.mozilla.org/en-US/kb/quarantined-domains

On that link:

Users can also control this behavior for each extension in the Add-ons Manager (about:addons) starting with Firefox version 116.

And also:

Search for the extensions.quarantinedDomains.enabled preference. [...] change its value to false

Also from #41825 (closed):

extensions.quarantinedDomains.list is a runtime, populated via remote services, so if we don't want to implement this in some form, then there's nothing else to do.

We also do not recommend any extensions other than those bundled: both of which are recommended by Firefox, so would not be exempted from any domains.

For this reason, I think we could leave the feature on. In the next ESR we'll get the granular settings. If users aren't happy, we can try to backport this change later, e.g. in 13.5. (But, spoiler alert, our list stays empty).

More remote setting to potentially purge for Mullvad Browser and maybe Tor Browser.

From what I understand, these aren't new remote settings, but add to the ones of addons. We already disable all the other remote settings, and indeed the list is already empty.

Personally, I think we should ship with an updated list pref value each release, not sure how you automate that

Usually Firefox includes dumps in each release, but it doesn't for this preference .

But I'm okay with having it empty. The Bug is quite opaque, I wonder if there are more reasons in the Jira we can't see.

We don't have a source of these settings either.

So, for the time being, I'd simply ignore this feature.

Maybe should we revisit for FF128-esr? Otherwise, we can close.

added Needs Review label and removed Next label

mentioned in issue tor-browser-spec#40062 (closed)

closed

marked this issue as related to tor-browser-build#40965 (closed)

marked this issue as related to tor-browser-build#40966 (closed)

removed Needs Review label