Security Alert Feature for Opening/Extracting Programs

[searchlight4759]

A good idea would be an option to have Sandboxie issue an alert when one attempts to open or extract a program that is contained within the sandbox.

Even better, would be Sandboxie's ability to prevent the contents from being opened or extracted.

Yes, the whole concept of Sandboxie is to isolate particular and possibly malicious programs but security would be hardened if these features could be implemented.

In other words, if one likes exploring the contents of the sandbox, and attempts to open or extract a program i.e. zip file contained within it, one could be exposing oneself to possible security issues.

A person needs to know as a rule, that they should not open or attempt to extract an isolated program outside of the sandbox unless they know it comes from a trusted source but I think "knowing" and "remembering" is not enough and reminders would be a great help and enhance the security provided by Sandboxie even more.

Thanks tzuk for a fantastic program

[Guest]

Even better, would be Sandboxie's ability to prevent the contents from being opened or extracted.

Alerts might be OK if they can be turned off as an option, but restricting access would severely limit the way I and other experienced users use SandboxIE.

For example, I often install programs in a sandbox and then extract selected files to create portable versions.

SBIE (Happy) User

[searchlight4759]

SBIE:

I agree with you, providing an enable/disable option for the user to receive alerts and/or disable executable programs contained within a sandbox would satisfy all needs.

[mizzmona]

I have no problem with alerting against -- or even completely restricting -- sandboxed file activation from outside of the sandbox. I think that's a very good idea.

Otoh, simple file operations (move, copy, delete) should, in my opinion, not be restricted. Optional alerts (if any) for these type operations would be my preference as well.

-M

[SBIE User]

I have no problem with alerting against -- or even completely restricting -- sandboxed file activation from outside of the sandbox. I think that's a very good idea.

Otoh, simple file operations (move, copy, delete) should, in my opinion, not be restricted. Optional alerts (if any) for these type operations would be my preference as well.

-M

That would work for me too.

SBIE (Happy) User

[mizzmona]

(Quoting me)

Dang you're fast, had to unedit my edit... (not that it made a difference)

[searchlight4759]

I have no problem with alerting against -- or even completely restricting -- sandboxed file activation from outside of the sandbox. I think that's a very good idea.

Otoh, simple file operations (move, copy, delete) should, in my opinion, not be restricted. Optional alerts (if any) for these type operations would be my preference as well.

-M

That would work for me too.

SBIE (Happy) User

I agree with both of you, a configuration as you have described would definitely work for me.

Thank you both for your inputs:).