LibreWolf

3158 readers

1 users here now

Welcome to the official community for LibreWolf.

LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. If you have any question please visit our FAQ first: https://librewolf.net/docs/faq/

To learn more or to download the browser visit the website: https://librewolf.net/

If you want to contribute head over to our Codeberg: https://codeberg.org/librewolf

founded 3 years ago

MODERATORS

[email protected]

How to block all 3rd part cookies on Librewolf by default? (feddit.it)

submitted 1 year ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Goodmorning, I have used for a lot of time Firefox. In the privacy settings I can change tracking protection preferences to normal, custom and strict protection. Actually I'm using Librewolf, but I can't see that option. What I liked of that option is that switching to custom I'm able to block all third part cookies. Librewolf doesn't block third part cookies by default. For example, when I log for work with Google and I enter in a page that uses the google session cookie, I can see in the bar that I'm accepting that third part cookie. Of course I can remove it, but when I close the browser and I open it again I'll get the same problem. So is there any way to block all third part cookies in Librewolf? I understand that due privacy reasons the tracking protection is set to strict by default, but why tou didn't put an option to block all 3rd part cookies? Anyway, sorry for my English, I'm still learning it, I wish the question is clear.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago

I was looking in the librewolf FAQ and I have fond that:

In LibreWolf we decided to enable Enhanced Tracking Protection, as it plays nicely with uBO and it can block some extra scripts. (...) Finally, there's no point in changing from strict to any other mode, as strict mode doesn't usually cause any kind of breakage, and changing to custom mode to block cookies will come at the expense of disabling partitioning: not worth it, so we decided to hide the UI that allows users to change this setting. You can instead whitelist specific websites from the urlbar.

The FAQ redirects then to this comment on codeberg:

(...)users who change to other modes, do that for two main reasons, according mostly to reddit posts:

-they read strict so they think that if something is broken they need to change that. in my experience it never turned out to be true.

-they switch to custom to block third party cookies, which disables isolation making all the rest of the privacy measures useless, because lowest hanging fruit. even if they use FPI what they are getting is outdated code and more breakage, not good. (...)

Apparently disabling 3rd part cookies brakes the isolation, so they have decided to remove that option. I think that this is the best solution they were able to implement, but i have some perplexities. I wish they will solve this problem in the future. Of course, if anyone can clarify that point we'll appreciate it ;-)