Does the better "compatibility" affect the SBIE ro

[Unknown_User_451]

I see that less and less programs conflict with the SBIE - SBIE becomes more "compatible" with more and more programs out there.

What does this mean security-wise?
Is SBIE v3 easier to escape from than the previous version?

I'd like to see someone doing the reliability tests against each new SBIE build.
I fear of "too compliant" SBIE that becomes penetratable by an accident.

[tzuk]

Is SBIE v3 easier to escape from than the previous version?

No, SBIE 3 makes it harder (I'd like to think, impossible) for something to break out of the sandbox.

The compatibility fixes recently were mostly really bug fixes. In other words, programs were not running well because Sandboxie was not doing its thing properly.

Some fixes are really about letting Sandboxie access third-party software, usually security software. But you're supposed to trust your security software. If you can't trust security software, what can you trust?

[Unknown_User_451]

Thanks, Ronen, good to know.

Do you pay attention to not having any code defects, like the vulnerable libraries or unsafe coding practices?
Do you use the Safer C or the similar?

[tzuk]

I am mindful about coding practices. I don't use any programming elements from third parties.

[Unknown_User_451]

What is your tool-chain?
Does it allow to specify the Safer C library?
(I heard that MS has advised everyone to switch to S.C. functions and that it itself was re-writing some code to take the advantages of more security)