The firefox feature of `--no-remote -P` is the way to do that, which has existed since before the chrome browser did. Old feature.

This feature is not meant to solve that use-case since if your case is security, you need separate browsers/contexts/proceses anyways.

Separate profiles in firefox implement separate profiles (which may all be independently open side-by-side in different windows).

This exchanges less secure/strong separation with better UX by intermingling.

Firefox is just choosing to support either set of tradeoffs there.

Old perhaps, but userfriendly this is not.

I wonder how many users understand the concept of profiles and the session isolation they provide, want to use them, yet find the command line too difficult to use.

Most user won't even be aware of the possibility of using profiles, ask any of your relatives.

While if you had a "Create a new profile" button that does it in one step and that they would advertise on install much more people would be using it, even if it's just for family members separation.

Old Netscape/Firefox builds used to start with the Profile creation/selection screen by default (which is the -ProfileManager CLI option that remains today) and someone can correct me if I am wrong, but the consensus seemed to be that it confused people more than it helped them.

The majority of people already separate family members with different user accounts on the machine or mostly just don't seem to care.

This seems to be the interesting UX compromise that the new "Container Tabs" is trying to meet "where they live": the users that could use some of the advantages of profiles without the full overhead of using multiple profiles. It will be interesting to see if the compromise is picked up by average users.

(Fwiw, I've used multiple profiles in Firefox off and on for decades but have yet to find a relative I'd recommend that to.)

That was then, and this is now.

In the old days, seperate profiles were used to seperate Moms browsing from Dad's browsing. Now, we need different profiles to browse: one for shopping, one for banking, one for work...

Seems to me that coders forget that people evolve. Same with Moxie saying that it is fine for WhatsApp not ticking the 'tell me when the key changed'-box by default because that confuses people. Perhaps it /did/ confuse people, when security was not a known issue. People tend to learn, in my experience. You can't say: "Well, we did an A/B test in 2002 and now we're done for the next millenium."

Uh, right, people could use one for shopping, one for banking, one for work, etc... but they'd like them all to be in the same window so they can switch between them as tabs... (It's funny when you realize that the old ProfileManager predates tabs.)

Which is where we arrive today with Mozilla's work on "container tabs". The code and UX evolve, too.

I'm not sure what your complaint here is, mverwijs? That Mozilla should test Firefox starting up with the ProfileManager again? Like I said, I think "container tabs" might be a good way to do this in a way that mainstream users might pick up and this will be interesting to watch.

(I guess one trick that might be interesting if there was a way to easily "graduate" from I know/love "container tabs" to "oh, the next thing I can try is profiles to do more complicated things", but I think the answer is that profiles will adapt more to work with "container tabs" UX than "container tabs" UX will adapt to the old profiles UX. Given "incognito" tabs in other browsers can be seen as a specialization of a "container tab"/"profile tab", I suspect mixing profile tabs in a single browser window is a UX that is here to stay.)

Since they're akin to user accounts on windows, I'd assume a decent number of users understand them.

Even though people don't use multiple-user-accounts too much anymore, it's still usually present in schools and in older family computers.

Conceptually they're very similar.

there are extensions like switchy that handle the UX part in a reasonable way.

I'm genuinely not trolling here: what are you worried could happen if you didn't do all of this stuff with the extensions and settings in your various profiles? What does it mean to trust a website?

From past experience, and the reason I browse with some fairly aggressive security settings (not the OP): I'm worried I could acquire a nasty rootkit-level virus.

I'm worried about that because I used to browse with no Noscript/similar, and then I got a infected by a rootkit, which I traced back to a new site I'd visited.

Since I didn't enjoy having to nuke my entire computer environment from orbit, I now have a rather locked-down browser.

I turn all of those Chrome features off everywhere anyways. I find the handlers to be especially annoying. Why the fuck would I want that? There's a reason I use Mail.app and it's not because I love using email in web views.

Isn't mailto: opening Mail.app for you?

yes, but Chrome bugs me about switching it to Gmail every time.

"I'd like to see these security levels built into browsers where the contexts are built around permissions and site trust rather than access to the user store (which is also important)"

I want to take it all the way to eleven and 'jail' a gui process (in this case, the web browser - any web browser). It gets its own filesystem root and its own IP BUT I don't have to pay the penalties of firing up a full blown virtual machine.

This isn't easy to do in the way that, for instance, jailing a daemon is easy to do ...

Further, even if I did have a workable recipe to jail a chrome process (and all of it's children) it would certainly only be for X. Maybe there's some recipe for that in OSX but it would be profoundly different. OSX doesn't even have the 'jail' command (although it does have chroot ...)

For a partial solution, have a look at "sandbox -X" (man 8 sandbox).

Agreed, although be aware that this is only available when you're using SELinux. By default that's Fedora/Centos/RHEL, not Debian/Ubuntu.

depending on your OS of choice, desktop containers using something like docker (e.g. https://blog.jessfraz.com/post/docker-containers-on-the-desk...) can achieve it and are a reasonably straightforward (for a certain value of straightforard) option (linux only unfortunately...)

> The images work by mounting the X11 socket into the container! Yippeeeee!

Well, yippee, now the application can read all keyboard input from that X11 socket, there goes your "sandbox"...

You really need Wayland to get a practical security benefit for GUI applications from containers.

You can already disable flash, javascript and cookies by site. That covers pretty much everything from site logins to WebGL.

you are using the wrong tool.

install NoScript in firefox and allow flash/etc per domain temporarily or permanently.

profiles/context tab is all about tracking. You just happen to successfully abuse one tool to your ends in one case.

I'd take a look at uMatrix, which is easier and more granular than NoScript (but lacks the more in-depth security features). It allows you to block/allow cookies, css, images, plugins, scripts, frames, and more on local/remote host basis.

For example, when visiting example.com you could allow scripts from example.com but not from gstatic.com, analyticshost.com, or shadylookingdomain.com. Yet at domain.com you could allow gstatic.com scripts and images because it embeds Google Maps.

It's all done in an amazing, quick GUI that provides a visualization of the rules. I wish all firewalls would adopt the UI.

NoScript is a pain to use and configure. And you need to finely tune it. With this profile method, you can have a "all-in" profile, and a "safe" one. This makes things much easier to manager.

1. install it. and close the annoying tab.

2. visit a site, click the noscript icon

3. allow the domains you trust.

no step 4.

how is this hard?

you only have to click the icon again if some site is not working.

> you only have to click the icon again if some site is not working.

And then you start realizing that blocking all scripts is a pain. You want just this script to work, but not this one. So you start filtering and it takes so much time.

Then often, a site is not working exactly right, and you don't know no-script screw you. Sometime you realize it after 10 minutes looking for something no-script removed. Waste of time. Then you for some time you want it one for a site, then off for the same site. And on. And off. And you have 30 tabs, then you have to jungle with the state of it.

where do you set those configurations? (handlers, hardware access, flash, pdf, webgl)

do you have a link to an official chrome help page?

also what chromium do you use? and where did you get it?

sorry for my ignorance.