Talking strictly about security, how would you rate multi-account-containers for compartmentalizing internet activity? By compartmentalizing, I mean if, for example, I click on link “xyz” on container “a”, and this link is somehow capable of accessing account “b” and compromise it. Except I have this account “b” logged in another container. Would the website be able to compromise the account? I know zero-days exist, but in a typical situation, would this extension improve security in this example or not?
So from a privacy perspective from a site in the browser looking at cookies, with or without containers it should not be able to see cookies from other websites.
However from a security standpoint if something breaks out of the browser with an exploit and infects the host system, it can read all of the browser data easily from any site in any container.
Total cookie protection (called “State partitioning” under the hood) is not totally total.
In order to resolve these compatibility issues of State Partitioning, we allow the state to be unpartitioned in certain cases. When unpartitioning is taking effect, we will stop using double-keying and revert the ordinary (first-party) key…
There are two scenarios in which Firefox might unpartition states for websites to allow for access to first-party (cross-site) cookies and other state:
When an embedded iframe calls the Storage Access API.
The documentation is… Confusing. This was the third time I tried looking into it, and the last two times I was much more wrong about how it actually worked.
Total Cookie Protection also protects more than cookies, FWIW.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Even without containers cookies are separated between sites: https://blog.mozilla.org/en/products/firefox/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/
So from a privacy perspective from a site in the browser looking at cookies, with or without containers it should not be able to see cookies from other websites.
However from a security standpoint if something breaks out of the browser with an exploit and infects the host system, it can read all of the browser data easily from any site in any container.
Total cookie protection (called “State partitioning” under the hood) is not totally total.
Good to know! Annoying that it doesn’t tell you that.
The documentation is… Confusing. This was the third time I tried looking into it, and the last two times I was much more wrong about how it actually worked.
Total Cookie Protection also protects more than cookies, FWIW.