Multiple different sandboxed instances of
Firefox Portable running concurrently in parallel. "Different" = each instance runs in a different sandbox (with different sandbox settings and content) under
Sandboxie-Plus. The
Forced Folders feature of Sandboxie-Plus lets me specify that any programs located in a folder (that I can specify) should be forced to always run sandboxed so, to get this to work with Firefox Portable, all I had to do was just specify my main folder of Firefox Portable. So, because I can wipe a sandbox totally clean with just a single mouseclick, each time when I want to make a more permanent change (e.g., in the settings and/or by updating Firefox Portable, manually, as it doesn't nag me about updates) I just temporarily rename this folder. So, next, when I run the program it doesn't run sandboxed until after I close it, rename the folder back again, and rerun. Also, I made it my default browser:
Another "trick" is that Firefox Portable lets me put a file named
FirefoxPortable.ini in its main folder. Putting the line
AllowMultipleInstances=true in this file enables multiple instances in Firefox Portable, and, this still works regardless of whether I choose to run it sandboxed.
By making multiple copies of my main folder of Firefox Portable, doing things like make all different changes to each copy (or different to some of them) before I run them sandboxed, run each different copy in a different sandbox and/or run the same copy in multiple different sandboxes concurrently in parallel I can do a lot more than what's already possible to achieve with the
Firefox Multi-Account Containers addon and/or with Firefox profiles. If anything, it adds an extra layer of browser protection. But I also wrote my own scripts (and a few small programs) to automate various tasks that depend on all this, not only for browsing the web. The sandbox location of some of my sandboxes points to a ramdisk. This ramdisk uses compact mode (a feature called
Dynamic Memory Management) which prevents the ramdisk's available free space from unnecessarily consuming so much RAM. Finally, due to the fact that Sandboxie-Plus doesn't
require a program to be stored in the sandbox before this program can run sandboxed (as it only needs to store content in the sandbox to isolate
changes that result from what's running sandboxed) it doesn't necessariy have to become a hog. (Even, if multiple sandboxes are actively used at once, i.e., "running concurrently in parallel".)
gs.statcounter.com
