Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
Comodo Sandbox (Auto-Containment) have a bug on Windows 10?
Message
<blockquote data-quote="AtlBo" data-source="post: 718377" data-attributes="member: 32547"><p>Funny thing about this to me is that I can't say it's a bug with Comodo. Well, the broken sandbox is a bug. However, I wonder if the limitation being set to partially limited could be tied to this bug somehow, as in any other restriction broke the sandbox beyond repair on W10. In that case, I guess it would be part of the broken sandbox bug.</p><p></p><p>The other thing I have considered is the difference between operating systems. Could Comodo have just decided that Partially Limited in Windows 10 will get you the same security as Restricted in former versions (i.e. W7)? Not going to put it past Comodo to decide something like this, especially if their view of the intention of the privilege elevation alert is to give you an opportunity to run the process in a more risky way. Maybe the difference with W7 simply reflects that they decided not to change it, thinking who cares or that W7 is less secure in the first place? That's how bonkers it can be not knowing what they are thinking. Just maybe Comodo is thinking this is the way to give you more security than actually running completely unrestricted under Windows system restrictions only <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite120" alt="o_O" title="Er... what? o_O" loading="lazy" data-shortname="o_O" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite119" alt=":rolleyes:" title="Roll eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /></p><p></p><p>Has anyone chronicled whether the sandbox breaks in Windows 7? Maybe that would provide some useful information on what might be happening with this bug if anyone is available to test. Thanks very much to [USER=28210]@Av Gurus[/USER] for following through with this bug with Comodo and for the thread. I am sure it means alot to Comodo at the important levels to hear concerns like this one...</p></blockquote><p></p>
[QUOTE="AtlBo, post: 718377, member: 32547"] Funny thing about this to me is that I can't say it's a bug with Comodo. Well, the broken sandbox is a bug. However, I wonder if the limitation being set to partially limited could be tied to this bug somehow, as in any other restriction broke the sandbox beyond repair on W10. In that case, I guess it would be part of the broken sandbox bug. The other thing I have considered is the difference between operating systems. Could Comodo have just decided that Partially Limited in Windows 10 will get you the same security as Restricted in former versions (i.e. W7)? Not going to put it past Comodo to decide something like this, especially if their view of the intention of the privilege elevation alert is to give you an opportunity to run the process in a more risky way. Maybe the difference with W7 simply reflects that they decided not to change it, thinking who cares or that W7 is less secure in the first place? That's how bonkers it can be not knowing what they are thinking. Just maybe Comodo is thinking this is the way to give you more security than actually running completely unrestricted under Windows system restrictions only o_O:rolleyes: Has anyone chronicled whether the sandbox breaks in Windows 7? Maybe that would provide some useful information on what might be happening with this bug if anyone is available to test. Thanks very much to [USER=28210]@Av Gurus[/USER] for following through with this bug with Comodo and for the thread. I am sure it means alot to Comodo at the important levels to hear concerns like this one... [/QUOTE]
Insert quotes…
Verification
Post reply
Top