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="n8chavez" data-source="post: 1035894" data-attributes="member: 90863"><p>[USER=62850]@danb[/USER], I did notice a couple more things:</p><p></p><p>1. If I already have an allow firewall rule and that app gets updated Cyberlock will create a new block rule (because the update is initially seen as unsafe because the hashes are too new), that Cyberlock created block rule will take priority over any allow rule. Since Windows Firewall doesn't use hashes there's no way of distinguishing between the rules. That's not good. I recently began having rclone issues and I could see why, and my configurartion remained the same. Cyberlock created a block rule for it. Would it be possible to not create a block rule if there is already a rule created for that .exe?</p><p></p><p>2. I assume with this re-branding you want everything to say Cyberlock now and not VoodooShield. However, the application icons (tray, desktop shield, etc.) still say "VS."</p><p></p><p>3. When I try and do a manual update check within Cyberlock, I get the below message saying I have no internet connection, although I clearly do. I also have no firewall rule blocking cyberlock.</p><p></p><p>[ATTACH]274611[/ATTACH]</p></blockquote><p></p>
[QUOTE="n8chavez, post: 1035894, member: 90863"] [USER=62850]@danb[/USER], I did notice a couple more things: 1. If I already have an allow firewall rule and that app gets updated Cyberlock will create a new block rule (because the update is initially seen as unsafe because the hashes are too new), that Cyberlock created block rule will take priority over any allow rule. Since Windows Firewall doesn't use hashes there's no way of distinguishing between the rules. That's not good. I recently began having rclone issues and I could see why, and my configurartion remained the same. Cyberlock created a block rule for it. Would it be possible to not create a block rule if there is already a rule created for that .exe? 2. I assume with this re-branding you want everything to say Cyberlock now and not VoodooShield. However, the application icons (tray, desktop shield, etc.) still say "VS." 3. When I try and do a manual update check within Cyberlock, I get the below message saying I have no internet connection, although I clearly do. I also have no firewall rule blocking cyberlock. [ATTACH alt="2023-04-16_08h49_25.png"]274611[/ATTACH] [/QUOTE]
Insert quotes…
Verification
Post reply
Top