3 ms·

How does this compare with using multiple profiles and the -no-remote flag? Does this manage only cookies, or does it also separate local storage (HTML5 session

by jqs79 9y ago

How does this compare with using multiple profiles and the -no-remote flag? Does this manage only cookies, or does it also separate local storage (HTML5 session/local/global/web sql database), webcache, window.name caching (if the same tab can use multiple profiles), web history, flash cookies, for those who still have flash installed, etc. People might get a false sense of security if all of these methods of saving data in the browser are not also separated along with cookies.

groovecoder 9y ago
Check out https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers#What_is_.28and_isn.27t.29_separated_between_Containers https://wiki.mozilla.org/Security/Contextual_Identity_Projec... for the details of what is - and isn't - separated between Containers.
- jqs79 9y ago
  Thanks. So it appears that most of it is separated, with the exception of web history and search and form data (which can be identifying). This was also interesting: "Users can log into multiple accounts on the same site, even when the site does not natively support concurrent sessions. ... Current solutions: Users open multiple browsers (this takes users away from Firefox). A user opens one account in Private Browsing mode (this has a limit of 2 accounts, and forces one to be ephemeral)." There is no mention here of the -no-remote flag which has been available for many years.
  - 482794793792894 9y ago
    Well, the vast majority of users have no idea of the -no-remote or -new-instance flags, let alone of Firefox profiles.
482794793792894 9y ago
Generally speaking, Container Tabs try to make you look towards the internet like several users while on your end it behaves like a single-user experience. So, things like history, bookmarks and add-ons are not separated by Container Tabs. And the technology behind this was developed by the Tor Browser devs and then uplifted into Firefox and reused for this, so this is a proper security/privacy feature, not something that only works on the surface.

by jqs79 9y ago

groovecoder 9y ago

Check out https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers#What_is_.28and_isn.27t.29_separated_between_Containers https://wiki.mozilla.org/Security/Contextual_Identity_Projec... for the details of what is - and isn't - separated between Containers.

jqs79 9y ago
Thanks. So it appears that most of it is separated, with the exception of web history and search and form data (which can be identifying). This was also interesting: "Users can log into multiple accounts on the same site, even when the site does not natively support concurrent sessions. ... Current solutions: Users open multiple browsers (this takes users away from Firefox). A user opens one account in Private Browsing mode (this has a limit of 2 accounts, and forces one to be ephemeral)." There is no mention here of the -no-remote flag which has been available for many years.
- 482794793792894 9y ago
  Well, the vast majority of users have no idea of the -no-remote or -new-instance flags, let alone of Firefox profiles.

482794793792894 9y ago

Generally speaking, Container Tabs try to make you look towards the internet like several users while on your end it behaves like a single-user experience. So, things like history, bookmarks and add-ons are not separated by Container Tabs. And the technology behind this was developed by the Tor Browser devs and then uplifted into Firefox and reused for this, so this is a proper security/privacy feature, not something that only works on the surface.