So I’ve been looking through a few threads about sandbox in regard to version 4 of Comodo. Now as far as I know it seems to be some kind of virtual environment. But I am still at a loss of how this helps?
Is it like some kind of shield? Like it’s still there but there is a barrier between your programs and the actual pc? Even so can someone explain the benefits of such things? Like suppose you have a program running in the sandbox that has already been infected but your security software has yet to detect it?
why should the sanboxie page explain how the comodo sandbox works?
the comodo sandbox is a restriction element, and NOT a sandbox like sandboxie.
if you do the same as what you can do with sandboxie, your pc can be infected in REAL, and the sandboxed programs in comodo sandbox have access to the internet (default setting).
its hard, having to see how much comodo has confused the users to this point, that they think its like the sandboxie sandbox.
i dont want to know how many people will get infected or get their data send by a “sandboxed” trojan, as long as they misunderstand the comodo sandbox.
for security reasons i disabled it.
if you suggest to read about sandboxie, then you should suggest to use IT.
if you want to see the “features” of the comodo sandbox, you have to look in a “kind of hidden place”: “programs in the sandbox, add”. there you see the scale of different settings. if you read the examples, you will definitely understand what the comodo sandbox is. just a restriction element for accesses, and something to reduce alarms (with some dangerous side effects).
if you do the same as what you can do with sandboxie, your pc can be infected in REAL, and the sandboxed programs in comodo sandbox have access to the internet (default setting).
I'm saying, that in principle that's how it, basicly how it works. Of couse, the features, settings, and the methods used operate differently.
Also comodo ISN’T a full sandbox either. Maybe it should be called something else in the mean time until it’s gets to be full sandbox. Or at least call it a beta or even a alpha version of it <–But’s that’s just an idea
And this, I think, is where a large number of the difficulties arise - that actual naming of the function.
Sandboxing, as a concept, has been around for years on many, many platforms. In essence, it’s a “playground” where you can fiddle with things without affecting a production system. In SAP systems, there is generally a client (SAP subsystem) setup for practising and this is called the sandbox or sandpit.
Sandboxing is becoming a far more common term in the wider Windows community, thanks in no small part to an application called Sandboxie. Sandboxie is a great sandbox application - probably one of the top two available so far for Windows. Because of this popularity and widespread fame, the specific functionality provided by Sandboxie (the app, not the concept) is sometimes perceived as how sandboxes work, and anything that doesn’t operate in the same manner as Sandboxie is doing it wrong.
The sandbox in CIS4 is not intended to provide the same functionality as Sandboxie. It’s similar but not the same.
I think, and I may be wrong here (definitely not unheard of ;)), that some people hear the term “sandbox” and immediately think of “sandboxie”.
Sandboxie is a great sandbox application - but it is not the only sandbox application in town.
Please understand this is not intended as a diatribe against Sandboxie or a defense of CIS’s Sandbox function. CIS’s Sandbox can be better and, IMHO, should get better. I also believe that it should have been called something other than “sandbox”. IMHO, it’s different enough to a traditional sandbox to warrant a different name, if only to help avoid confusion.
I’m merely concerned that some users may be getting confused between the concept “sandbox” and the application “sandboxie”.
