Comodo + Sandboxie sandboxing applications?

I have currently set both Comodo and Sandboxie to force Digsby into their sandboxes.

Security benefits of this?
Security issues?

It's important to note that for Digsby to work I had to have Sandboxie give access to Comodo's virtualroot/digsby folder.

I think there are possible benefits for Digsby's case because normally you have to give access to the real file system whereas now I've given access to Comodo's virtualized "real" file system.

 

You forgot compatibility issues. I only use Comodo's automatic sandbox.

 

Compatibility issues would fall under Security issues I would think - if something crashes it isn't protecting me.

I haven't come across anything yet.

 

The first negative thing that would come to mind for me would be looping. If one virtual environment is virtualizing another virtual environment, does it become a never ending loop within each? Just a thought that I had, but maybe worth looking at.

Sul.

 

I think it becomes two virtual environments with some middle ground, like a Venn Diagram.

I'm not even sure how it's working >_<

I'm monitoring CPU and stuff in case there's ridiculous conflicts. None that I'm seeing.

 

If you click on a link within Digsby, is the browser also sandboxed?

 

The browser runs sandboxed in Digsby sandbox if all programs are
allowed start/run/internet or if the sandbox is restricted and the
browser is allowed start/run/internet access.

Bo

 

You won't like my opinion but since you are asking globaly - one or the other, but not both. Sully is being more diplomatic than I although I tend to think he doesn't really like the idea of using both in tamdem either

Just imagine the stable fortress you could build with either one of those (fwiw, I'd choose Sandboxie) combined with AppLocker and a properly configured Windows fw w/advanced security restricting both incoming and outgoing comms, kinda like my setup Anyway, and in all seriousness, if it works for you without stability or conflict issues, and you like it, then go for it

 

Chrome isn't allowed in the Digsby sandbox. I may change this eventually.

@Wat
Yes, I can imagine some issues arising. The thing is I like that it keeps my Java and Chrome separated, which Sandboxie doesn't seem to do on its own. And I like that Digsby's access to the real system is cut off when normaly it would need direct access to real-system folders.

I'll check things out.

 

Well personally it seems to be overkill and I see the compatibility issues rising eventually. But to echo wat's comment, if it works for you without issues, then go for it.

 

Yeah the thing is that I don't want to remove Comodo anyways - I still like the cloud scanner and I still like the firewall and defense+ HIPS.

We'll see. If there are any issues with the sandbox I'll remove Comodo's.

 

I never was talking about removing Comodo. I was talking specifically about using two sandboxes.

 

I know. But if I have Comodo installed I want to get the most out of it.

 

Ok then.

 

Unnoticeable, unknown issues are the ones that, if I was you, I would
worry about. The issues that don't have tell tale signs are the ones
that can hurt you when you need SBIE to be on top shape but instead
Sandboxies protection has been watered down and you dont even
know about.

Bo

 

Unfortunately I have no idea if those issues exist. They very well may not. No real way to test for it.

 

I just tried it out, with file and registry virtualization disabled. There shouldn't be any problems, and I don't see one. The reason I do that is because sometimes Firefox open unsandboxed whether I like it or not.