Launch Chrome profiles in their own sandbox

Mr.X

Member
Staff member
I've been doing this using dedicated and customized shortcuts to run different Chrome profiles in their own dedicated sandbox.

Now I wonder if it's doable to launch Chrome profiles from its own built-in menu. I guess Sandboxie would need to intercept the chrome.exe cmd line pointing to a profile, then Sandboxie redirect to the dedicated and specified sandbox. Don't know.

1.png
 
I've been doing this using dedicated and customized shortcuts to run different Chrome profiles in their own dedicated sandbox.

This is how it works and what is going to be suggested when someone wants to separate the profiles in different sandboxes.

Now I wonder if it's doable to launch Chrome profiles from its own built-in menu. I guess Sandboxie would need to intercept the chrome.exe cmd line pointing to a profile, then Sandboxie redirect to the dedicated and specified sandbox. Don't know.

I don't know, how difficult it would be. If you use the same sandbox for all profiles, you should be able to use the internal menu. Since Chrome has already started, it appears to me that the breakout process feature of Sandboxie would need to get more specific. Then chrome.exe would launch another instances of chrome.exe with the desired profile and Sandboxie would need to not only take a look at the process, but also its command line. (Chrome starting a fresh instance, is an assumption I made.)

What I wonder about is how reliable Sandboxie can intercept and redirect such profile changes.

Edit: Maybe David or someone else, like offhub, who contributed code to the project can assert how feasible this is.
 
Chrome uses interprocess communication (IPC) to launch new profiles rather than a traditional process creation with visible command-line arguments, Sandboxie cannot intercept and redirect the new profile to a different sandbox. (only tested from hamburger menu)
 
Back
Top