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
Inactive Support Threads
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
Software
Security Apps
VoodooShield
VoodooShield CyberLock 7.0
Message
<blockquote data-quote="danb" data-source="post: 995388" data-attributes="member: 62850"><p>I spent some time on this and there are several ways to fix this issue.</p><p></p><p>1) The best option is for devs to not have their apps throw powershell command lines from a randomly named C:\Windows\Temp\ folder. If this can be fixed in CD by possibly moving the binary from Windows Temp to Program Files, that is by far the best option.</p><p></p><p>2) Another option would be for VS to add special rules to the contextual engine for CD. There are currently only around 20 or so special rules in our contextual engine, and they all are related to Microsoft, and most to MD <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" />. This is not the best option, but if all else fails we might consider this.</p><p></p><p>3) Another great option is to simply put VS in training mode, then click around in CD for 1-2 minutes. VS will quickly learn the command lines so it will not block them in the future. Or just keep VS on Smart or Always ON and allow the 5-6 blocks it creates. I tested this 2 different times, once while in Training Mode (no blocks) and once in Smart ON Mode (5-6 blocks). The command line algos in VS are pretty smart… the command lines do not have to match exactly in order to auto allow a slightly different command line. So 5-6 blocks is about all you will experience.</p><p></p><p>BTW, the training on the new VoodooAi is going really well and should be ready in 3-5 days!</p></blockquote><p></p>
[QUOTE="danb, post: 995388, member: 62850"] I spent some time on this and there are several ways to fix this issue. 1) The best option is for devs to not have their apps throw powershell command lines from a randomly named C:\Windows\Temp\ folder. If this can be fixed in CD by possibly moving the binary from Windows Temp to Program Files, that is by far the best option. 2) Another option would be for VS to add special rules to the contextual engine for CD. There are currently only around 20 or so special rules in our contextual engine, and they all are related to Microsoft, and most to MD ;). This is not the best option, but if all else fails we might consider this. 3) Another great option is to simply put VS in training mode, then click around in CD for 1-2 minutes. VS will quickly learn the command lines so it will not block them in the future. Or just keep VS on Smart or Always ON and allow the 5-6 blocks it creates. I tested this 2 different times, once while in Training Mode (no blocks) and once in Smart ON Mode (5-6 blocks). The command line algos in VS are pretty smart… the command lines do not have to match exactly in order to auto allow a slightly different command line. So 5-6 blocks is about all you will experience. BTW, the training on the new VoodooAi is going really well and should be ready in 3-5 days! [/QUOTE]
Insert quotes…
Verification
Post reply
Top