VoodooShield CyberLock 7.0
- Thread starter danb
- Start date
So I can have a stable beta but only a "download Cyberlock"? *duck*
For me the wording would make more sense the other way around. Like "download stable cyberlock" or "newest" beta.
Isn't the purpose/definition of a beta to find flaws and be aware that problems can happen?
- May 31, 2017
- 1,672
- May 31, 2017
- 1,672
We can word it however it makes sense, I am fine with it either way. Many years ago our beta versions were probably not stable enough for the public. But the last 6-7 years, they have been stable, and I just didn't want anyone to think they would be downloading a version that was not stable.
We should not have to make any major changes for the foreseeable future, but if we do, then the beta versions might not be all that stable. If this happens, we will note it on our website.
@danb CyberLock installation should fix the problem of enabling "startup boost" in Edge. Installing CL activated the startup boost setting, causing a few settings changes in Edge with the lock icon. I used my backup program to restore Edge settings to their original state.
- May 31, 2017
- 1,672
Sounds good... I just disabled this so it won't be an issue anymore, and it will be included in the next version. BTW, when you uninstall CyberLock, it should set the startup boost settings to default, thank you!
- May 31, 2017
- 1,672
Hey Guys,
Here is the latest CyberLock! I figured out why the WhitelistCloud scan was taking forever and making the CPU fan spin louder on some machines, and this issue is completely resolved now. My scan was at around 600 seconds, now it is around 35. I have to continually reset my whitelist for development purposes, so my whitelists are always small, like around 200. FYI, WhitelistCloud typically scans around 4-5 items per second.
Basically, when we added the extra blocked file types, a few of those types happened to be very large files, like 20 gigs or so. This issue started happening on my machine recently, and in my case it was .vhdx files that were 20 gigs. What was happening was that WhitelistCloud calculates the hash of these files during the scan, and well, it takes a very long time to calculate the has of a 20 gig file. Anyway, the fix was to ensure that only files that are actually WhitelistCloud file types are scanned by WhitelistCloud.
There are also several other optimizations and tweaks, and I think we are in great shape for a public release, but if you guys find anything please let me know. The startup boost tweak has been removed as well.
I am also still working on the WDAC Lockdown component. It looks like it will be finished for DefenderUI Pro in the next 4-5 days. Once everyone gets to experience this new feature, we can figure out if we should add it to CyberLock or not.
CyberLock 7.76
SHA-256: 49f8d267fe03e27084caac5c2a4d92fcb35fc786a12840b3ecd67430738572c6
Thank you guys!
Dan
Here is the latest CyberLock! I figured out why the WhitelistCloud scan was taking forever and making the CPU fan spin louder on some machines, and this issue is completely resolved now. My scan was at around 600 seconds, now it is around 35. I have to continually reset my whitelist for development purposes, so my whitelists are always small, like around 200. FYI, WhitelistCloud typically scans around 4-5 items per second.
Basically, when we added the extra blocked file types, a few of those types happened to be very large files, like 20 gigs or so. This issue started happening on my machine recently, and in my case it was .vhdx files that were 20 gigs. What was happening was that WhitelistCloud calculates the hash of these files during the scan, and well, it takes a very long time to calculate the has of a 20 gig file. Anyway, the fix was to ensure that only files that are actually WhitelistCloud file types are scanned by WhitelistCloud.
There are also several other optimizations and tweaks, and I think we are in great shape for a public release, but if you guys find anything please let me know. The startup boost tweak has been removed as well.
I am also still working on the WDAC Lockdown component. It looks like it will be finished for DefenderUI Pro in the next 4-5 days. Once everyone gets to experience this new feature, we can figure out if we should add it to CyberLock or not.
CyberLock 7.76
SHA-256: 49f8d267fe03e27084caac5c2a4d92fcb35fc786a12840b3ecd67430738572c6
Thank you guys!
Dan
- Aug 19, 2019
- 1,025
Installed and working fine at my end. I regularly have aroud 600 in my whitelist. Maybe a feature like an automatic trimming of whitelist, say ones not used within the past week or two but that's just a thought. Thank you for an amazing product!
Similar threads
