- May 31, 2017
- 1,771
Yeah, marketing is not my greatest strength@simmerskool The nice thing about Dan is that he is more a techie than a marketeer, "the new and improved cyber lock, now without unnecessary blocks"![]()
Yeah, marketing is not my greatest strength@simmerskool The nice thing about Dan is that he is more a techie than a marketeer, "the new and improved cyber lock, now without unnecessary blocks"![]()
Hmmm, this is very, very odd. I am not seeing ANY exceptions / errors for any CyberLock version in our logs. The only errors I see are from a few users still running VS 7.36, for errors that have already been fixed.The "Watchdog Violation" BSOD occurred when I attempted to use CyberLock on Windows 11. I booted into Windows after a couple of tries. The solution to the BSOD problem was to uninstall CyberLock.
I'm testing security software with no other installations. The next time I attempt to use CyberLock, I'll report any error information.Hmmm, this is very, very odd. I am not seeing ANY exceptions / errors for any CyberLock version in our logs. The only errors I see are from a few users still running VS 7.36, for errors that have already been fixed.
If you could provide more info, I would certainly appreciate it. Either a screenshot or a C:\ProgramData\CyberLock\DeveloperLog.log file.
No other user has reported this error. What other security software are you running? Thank you!
Thank you, I just tested Handbrake. FYI, the installable version of Handbrake is considered safe, but the portable version is not.Here's something interesting, Cyberlock allows apps to run knowing they are not safe. As you can see from the screenshot below, Cyberlock's whitecloud does not see Handbrake as safe. Yet Handbrake is able to run just fine. Now, and I know I must be missing something, but isn't the entire point of Cyberlock to prevent things from running that are not deemed safe. Again, I assume this is user error and that my settings are wrong. How can I prevent this?
View attachment 276292
Also, as always, cute doggo @danb.
Are those applications not signed?Well then I'm confused. The version of handbrake I'm using, 1.61. is not portable. So you're saying it should be seen as safe, but WC doesn't? Also, this happens with a lot of applications after I update them, like Librewolf, Poppeeper, Sabnzbd, etc. All of those are not listed as "safe", and yet are able to execute just fine. I always keep Cyberlock set to "Always On."
Are those applications not signed?
With most of those, CyberLock / VoodooShield considers them safe (correct), but WhitelistCloud complains of the missing signature.
Sorry, I was talking about the Handbrake installer... it is considered Safe by WLC and VoodooAi. After reading this post I was thinking, hmmmm, maybe the Handbrake executable that is installed is what WLC is flagging as Not Safe. And sure enough, that is the case. There are tons of different scenarios that could have happened in your case, but my best guess is that Handbrake was already installed, so VS auto allowed it because it matched a digital signature that was already on your whitelist, but then out of an abundance of caution, WLC is telling you that it is not safe. There could have been other things at play, but this is my best guess. You can always look in the C:\ProgramData\CyberLock\DeveloperLog.log, and it will tell you why a certain item was allowed. Thank you!Well then I'm confused. The version of handbrake I'm using, 1.61. is not portable. So you're saying it should be seen as safe, but WC doesn't? Also, this happens with a lot of applications after I update them, like Librewolf, Poppeeper, Sabnzbd, etc. All of those are not listed as "safe", and yet are able to execute just fine. I always keep Cyberlock set to "Always On."
Yes, both VoodooAi and WLC are influenced by Digital Signatures. Sometimes the signature affects the verdict a lot and sometimes it does not, it all depends on the file and 400 or so other features in the machine learning modelAre those applications not signed?
With most of those, CyberLock / VoodooShield considers them safe (correct), but WhitelistCloud complains of the missing signature.
If you send me the exact steps to reproduce, I can take a look at this. Please keep in mind that the Rules feature will never be able to behave exactly the way every single person expects them to behave, although I try to structure them so they make the most sense to the most amount of people. Either way, I would be happy to look into this if you send me the steps to reproduce.Right. But that's my point. If something is not signed, if it's seen as "not safe" shouldn't it be blocked by default? Or, are you saying that the WC designation is not correct, according to Cyberlock's AI used by the rules wizard? If that's the case, I should be able to override the AI via rule and have things deemed "not safe" blocked. Right? But that doesn't happen. Even if I create a rule to block everything unsafe or unknown, bypassing signatures or AI, the file can still execute.
View attachment 276331
Yeah, this is what I think is happening to @n8chavez, but it is hard to say for sure without knowing every single detail, thank you!I am not so sure WLC blocks exe, but it does provide notice of running apps that might not be safe. then up to user to dig deeper to figure out if the maybe "not safe" is really not safe. One example that comes to mind, mullvad vpn installer is signed and safe, but when you install it, and then run the vpn exe which is not signed WLC turns red and gives "not safe" warning. Then you have the option of closing that app, or researching it & adding it to your whitelist (and to the cloud database gets updated too I think), but yes Dan can explain better.
There were no CL errors in Event Viewer upon my inspection. I had a smooth reinstall of CL this time with no problems. I'm enjoying CL. Should I combine it with a firewall, or is the Windows Firewall enough?Sounds great, thank you! If there is an error, maybe there is an entry in the Windows Event Viewer, or maybe a bug check / dump.
Sounds great, thank you for letting me know! If there are ever any issues, please let me know.There were no CL errors in Event Viewer upon my inspection. I had a smooth reinstall of CL this time with no problems. I'm enjoying CL. Should I combine it with a firewall, or is the Windows Firewall enough?