Question about COMODO Sandbox.
- Thread starter nsm0220
- Start date
- Status
- Dec 4, 2013
- 2,800
Although I'm not familiar with Comodo's sandboxing,
I think the principle is similar to other forms of containment. I'm using Sandboxie now. This essentially means that unless you have recovered an infected file or app, & already run said file outside of the sandbox, your system should remain un-exposed, unchanged, & thus safe. Deleting the contents of the sandbox flushes all un-recovered files away which should leave your system's state unchanged. Even new additions such as extensions & extracted software programs run in a sandbox should be safe. Any pre-existing infections cannot be helped by containment. I hope this helps.
I think the principle is similar to other forms of containment. I'm using Sandboxie now. This essentially means that unless you have recovered an infected file or app, & already run said file outside of the sandbox, your system should remain un-exposed, unchanged, & thus safe. Deleting the contents of the sandbox flushes all un-recovered files away which should leave your system's state unchanged. Even new additions such as extensions & extracted software programs run in a sandbox should be safe. Any pre-existing infections cannot be helped by containment. I hope this helps.everything in the sandbox/kiosk is deleted if you clean it, privileges limitations is active only when you run the file
- Sep 12, 2013
- 454
I had an horrifying experience with comodo which simply lead me to a series of blue screens and ultimately Windows image recovery
I had an horrifying experience with comodo which simply lead me to a series of blue screens and ultimately Windows image recovery
welcome to the club ^^
- Dec 4, 2013
- 2,800
- Feb 23, 2014
- 3,319
Same with me but :I had an horrifying experience with comodo which simply lead me to a series of blue screens and ultimately Windows image recovery
- Status
