You actually can do something like this with Firefox. If you load Firefox with the "-ProfileManager" switch (and you don't have another Firefox window open; see below for how to get round this), it'll open a window where you can choose your user profile. You can create and delete profiles from there, and a new profile is exactly the same as a completely new browser installation. (This includes any settings you may have for automatic browser updates; if you've turned these off on your normal profile, the first thing you should do on the new profile is turn off the automatic browser updates again, as browser updates are global and not per-profile.)

If you like, you can uncheck the "Use the selected profile without asking at startup" checkbox to have the window show up every time you start Firefox (which is defined as loading Firefox when there's no Firefox window already open). Doing this has the additional side benefit that if an application tries to open Firefox and load a new URL when you don't have any Firefox windows open, you'll be alerted to it by the Choose User Profile box - very useful if your normal profile takes a long time to load!

If you want, you can add the "-no-remote" switch to tell a new Firefox process not to connect with any existing one, which will allow you to open a new profile in a different browser window while you've still got the original running in other windows. However, those windows will share the same taskbar grouping, so I'd recommend you apply a different theme to the new profile to allow you to distinguish the two.

(Note: You should not use "-no-remote" by default, as a browser profile can only be open by one process at a time and you won't be able to open new windows through your shortcut icon.)

Of course, none of this will defeat the multiple-browser fingerprinting techniques mentioned in the article, but it's still incredibly useful.

I'm not sure if there's an equivalent in Chrome, or at least one that goes as far as Firefox does.

> I am reminded that what I really want is the ability to jail/chroot a browser.

Sounds a bit like local Docker for browsing?

Everyone would download the same Chrome container with the exact same clean config and software rendering so the canvas/WebGL fingerprinting yielded nothing?

Logging in to the Guest account on OSX accomplishes what you want, no?

Some of the fingerprinting involves not the user-controlled configuration of the machine, but hardware-related aspects like the canvas fingerprinting which looks at pixel level details of a small rendered figure. That combined with IP address will go a long way.

"Logging in to the Guest account on OSX accomplishes what you want, no?"

No ...

That is, unless I can easily script the destruction and recreation of the guest account, and automated install and configuration of my chrome setup ...

The idea here is that I set up chrome just how I want it and deploy and redeploy that "container" over and over - destroying it and recreating it after each use. Possibly with multiple instances running simultaneously ...

When a Guest logs out, any files they created are destroyed, including cookies and browser histories. But I don't know of a way to have multiple instances running sumultaneously.