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 Firewall Plays with RATs
Message
<blockquote data-quote="ForgottenSeer 98186" data-source="post: 1024562"><p>If it is such a usability issue, then why does Microsoft block interpreters itself?</p><p></p><p>How often are cscript, wscript, or powershell needed during install or uninstall routines? Less than 1%? Less than 0.1%?</p><p></p><p></p><p>There is no whack-a-mole needed.</p><p></p><p>[ATTACH=full]272868[/ATTACH]</p><p></p><p>The list of core Windows processes abused by threat actors on unmanaged (home) desktop systems has not changed in a long time. The "new" OneNote "malware" would have been stopped before it got started by the Microsoft default blocklist.</p><p></p><p></p><p>The mechanism of auto-sandboxing is easier, but then the Comodo sandbox gives no feeback whatsoever to the user about what is running inside the virtual environment. There is the potential (likely a small one given the type of user who will actually use Comodo) for a user to whitelist a file because it "appears" to do nothing malicious inside the sandbox.</p><p></p><p>But I do agree with you, with CF configured with your recommended settings it is so easy for those that know Comodo. As far as "ease-of-use." Meh. Just look at the hundreds of users that come here to MT and have to ask questions about Comodo. Your configuration videos are easy enough for a user to follow, and yet still, it is not so easy for some users.</p><p></p><p>All that said, it is up to the user to decide which solution works best for them personally.</p></blockquote><p></p>
[QUOTE="ForgottenSeer 98186, post: 1024562"] If it is such a usability issue, then why does Microsoft block interpreters itself? How often are cscript, wscript, or powershell needed during install or uninstall routines? Less than 1%? Less than 0.1%? There is no whack-a-mole needed. [ATTACH type="full"]272868[/ATTACH] The list of core Windows processes abused by threat actors on unmanaged (home) desktop systems has not changed in a long time. The "new" OneNote "malware" would have been stopped before it got started by the Microsoft default blocklist. The mechanism of auto-sandboxing is easier, but then the Comodo sandbox gives no feeback whatsoever to the user about what is running inside the virtual environment. There is the potential (likely a small one given the type of user who will actually use Comodo) for a user to whitelist a file because it "appears" to do nothing malicious inside the sandbox. But I do agree with you, with CF configured with your recommended settings it is so easy for those that know Comodo. As far as "ease-of-use." Meh. Just look at the hundreds of users that come here to MT and have to ask questions about Comodo. Your configuration videos are easy enough for a user to follow, and yet still, it is not so easy for some users. All that said, it is up to the user to decide which solution works best for them personally. [/QUOTE]
Insert quotes…
Verification
Post reply
Top