@danb ... why do I have to reduce (
Maximum to Typical) my daily rider router Security to reach Cuckoo. Um, does VoodooShield need
Typical for other VS functions.
I'm not sure... are there descriptions for each of your router levels? If so, if you post them I can look and see if there is a clue in there somewhere.
Here is a quick update... I have been having all kinds of "fun" trying to figure out the regional conversion issues. I am absolutely terrible with troubleshooting these types of issues, so if I cannot figure it out soon, Alex will help me figure it out... he is great with that kind of stuff.
Once this is finished, there are 4-5 other bugs I need to finish fixing, then we should be good to go.
Also, please keep in mind that VS 4.0 will temporarily have a few more blocks then 3.59... but over the next 2-3 weeks I will be refining the code, and the blocks will disappear soon. See, when redoing a lot of the code for VS, I tightened our locking mechanism even more, and now we have to find ways to safely allow items that should not be blocked. Here is one example... remember when I was talking about how VS 4.0 now also compares the parent process when checking the whitelist? That tightens the lock even more, but it will also temporarily produce a few more blocks, until I get a chance to refine the code. It is a little bit of a tedious process, but it will be worth it in the end.
VS has always been about creating the absolute tightest and strongest lock possible, while still remaining user friendly... as demonstrated earlier this year in test videos.
BTW, I also added logging for all of the blocks that users are experiencing. On one occasion I had an odd series of blocks with VS 4.0... but other than that, VS 4.0 has been quiet as a church mouse and has had zero bugs / exceptions. But anyway, once I see what is being blocked, it will be super easy to fix. I would bet that there are probably 2-3 bugs that are causing the blocks for users.
Also, a few people have asked about the blacklist scan... VS 3.59 scanned the file with the blacklist and VoodooAi, then stored the results in the VoodooAi cloud database. This is because the VoodooAi results will never change until the machines are retrained... which is a good thing.
VS 4.0 does the same thing, but now it also checks the current blacklist results each time to see if they have changed, and if so, updates the results. So basically, now the blacklist scan will always contain the most current results.
Thank you guys! I really hope we can wrap everything up in the next few days!!!
I remember we sort of agreed over on That Other Site that really the only apps of any consequence are browsers, simply because they offer the most opportunities for network interaction. OTOH, where are we on IRC etc?
