tzuk: Would be possible to add a feature to set a limit to the number of sandboxed processes?

No. What would be the use of that?

If the answer is no, why to explain the use of that?

I guess I'm curious.

I don't understand. That other topic says a program (which happens to be sandboxed, but not necessarily) can't be terminated while csrss.exe is displaying a message box on behalf of that program.

How is limiting the number of programs running in a sandbox at any one time going to help with that?

I meant malwares that create tons of processes to try to collapse the system.

Being able to set a limit to sandboxed processes would "fix" that problem when processing such malwares.

OK, maybe no need for a hard limit: I might be able to introduce small delays when a lot of programs are created during a short period of time. But I should tell you, I am not considering this a top priority.

That sounds good enough, thanks!

I will find an example you can use to work with.

Oh, no need for that. A batch file that spawns two instances of itself should be enough, and would be trivial to create.

Will you include this feature in 3.43.x betas?

Setting a hard limit is a good thing though, becuase for the casual user, surfing the web may not take notice if the malware that slips through starts initiating a huge number of processes even at a slower rate (due to the intentional delay system you will introduce. ) I see the usefulness of it when intentionally testing a POC, but most people dont tend to check the sandboxie control until the end of their browsing sesssion, even if that.

Of course Im not aware, but if doing so will lead to technical barriers in order to put such a restriction in place, then please tell us.

An interesting request, but one that I'm not fussed about. Almost all my sandboxes have start/run restrictions in place anyway, meaning only the processes I choose are allowed to start/run.

Maybe in 3.45.xx