inherit (not merge) sandboxes

Ideas for enhancements to the software
Post Reply
Posts: 50
Joined: Sun Mar 09, 2008 4:51 pm

inherit (not merge) sandboxes

Post by v2y » Sun Aug 08, 2010 11:53 am

Imagine like this:

Sandbox A : dotnet runtimes installed
Sandbox B : flash runtimes installed
Sandbox C : suspicious software 2 that needs dotnet
Sandbox D : suspicious software 1 that needs dotnet, and flash

And imagine Sandbox B and C inherits Sandbox A,B files, registry entries, and *some of* settings like this:

Code: Select all

[Sandbox C]
Inherit = Sandbox A

[Sandbox D]
Inherit = Sandbox A:Sandbox B	; imagine %PATH% ;-)
This function might lead Some race conditions/infinite loop with looking up objects,
so this function may be placed in .INI settings *only*, at first, I think.

Users must take responsible for tricky (and cool) settings.

Posts: 28
Joined: Tue Oct 29, 2013 4:07 am
Location: Deutschland

Re: inherit (not merge) sandboxes

Post by DocMAX » Mon Nov 30, 2015 8:06 pm

second this feature

Sandboxie Support
Sandboxie Support
Posts: 3523
Joined: Thu Jun 18, 2015 3:00 pm
Location: DC Metro Area

Re: inherit (not merge) sandboxes

Post by Craig@Invincea » Tue Dec 08, 2015 9:01 am

is is way the Config file is easily edited. For users to do what they wish. You can copy settings from one SB to another. But it's all or nothing. Otherwise, it's up to the user to customize each SB as they wish.

Adding more to it increases the chances of problems, compatibility, etc.

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests