VoodooShield/Cyberlock

If you need a Pro license, please let me know!

 

Ooops, didn't see that, thank you TH!

 

Cool, I will download Otter in a few minutes and see if I can reproduce this oddity. Thank you!

 

Cool, thank you for letting me know!

 

Very cool, I am happy you like it. Please email me at support@voodooshield.com and let me know what your email address is for your account and I will add some years to your subscription. Thank you!

 

That should be fixed... either in the current beta or the next release. Thank you!

 

Yeah, I added a link instead of a button for FP, but you can also make it a button in Settings / Advanced... the last option. Thank you!

 

Oops, I didn't see that, thank you for the help!

 

Cool, thank you for mentioning that!

 

I haven't being using VS since I last posted in this thread...but, the BSOD problem I was having with WSA has been rectified. So, I will reinstall the latest VS beta and see how it is.

 

It means VS killed a virus before it could execute.

 

Yeah, I am still working on that. It appears that it is the obfuscation that is causing the problem. I will see what I can do about it. Thank you!

 

Hey Mantra, I am not sure what you mean by tests. I think you mean has VS ever been professionally evaluated by a testing lab. If so, no, not yet, but it will be soon!

Sure, you can add folders in Settings / Custom. Thank you!

 

Yeah, that is how VS is designed... it is a lock and really the lock should be turned off when installing new software. I will post more about this in a sec, thank you!

 

The issue turned out to be that the option in Settings / Advanced “Do not whitelist items in the appdata directories” was checked. I should probably remove this feature since we do not need it anymore since we added hash comparison as well awhile back.

But selecting Always On Mode (which is basically “locked down”), and changing the settings to basically not allow anything, and then trying to install something new, and expecting VS to allow everything perfectly… honestly, that will never work properly. And really, if I wanted to make VS run poorly, that is easy to do, all I have to do is tweak all the settings to not automatically allow new stuff and put VS in Always On mode.

VS really is designed to function optimally in smart mode… that is what VS is all about. Once your computer is well trained… say a month or so, and you do not want to install anymore software, then put it in always on mode. For testing purposes, that is a totally different story, because adjusting the settings and trying every conceivable option helps me to work out any bugs that I might not have discovered otherwise.

The ironic thing is, it probably would have worked either way if the digital signature thumbprint from the 2-3 webroot executable files would have match, but for whatever reason, they don’t. I am not sure if this is by design for security reasons on Webroots part, or if it is just an oversight. It also would have worked if VS could have detected Webroot’s installer, but I am assuming it is a special custom installer, so VS will have a hard time detecting it. See, if VS would have detected an installer, the Install button would have been shown instead of the Allow button, and VS would have shut off during installation, and turned back on when the user returns to a web app, and is again at risk.

The thing is, VS has to balance user friendliness with security. If VS were to allow a processes that should have been blocked, then people would be upset about it, understandably I might add. So I like to error on the side of caution, and would rather VS block something if there is any question at all. On the other hand, people install VS and adjust the settings so that their computer is totally locked down, but then do not understand why they cannot install anything.

Voodooshield is preconfigured with optimal settings and they settings should only be adjusted on unique occasions.

So most users probably should Install VS and leave it in its default settings and in smart mode. And when they install new software, they should close all of their running programs, ESPECIALLY security software, before installing new software. During installation, a lot of installers usually have to perform several tasks that might be blocked by your security software. If you are not sure if something is good or not before installing, drag and drop it to VS first. Thank you!

 

Very cool, thank you!

 

Hmmm, that is odd, is VS registered? Like, are you running VS Pro? And it is only on your tablet? Thank you!

 

Hey Kees, the C++ runtime is 2010 for all versions of Windows, but the GUI and service .net code is 2013 for Windows 8 and 8.1, and 2010 for Windows 7 and below for now. I am just trying to keep everything as native as possible, not that it really matters. Also, we will be implementing the KMD sometime in the near future, and at that point we will probably use the 2013 C++ runtime for the KMD, so the 2010 C++ runtime will no longer be used. We could change it now, but then all of our users would have to install the 2013 C++ runtimes the next time they update VS. Thank you!

 

Yeah, you can turn UAC on and off and see if that fixes it. When VS turns off UAC during installation, it basically does the same thing as the user toggling it on and off. Thank you!

 

Nope!

That didn't fix it, but restoring from an image backup did.

 

You could remove it, or just add programdata folder to the description so users will know they will not be able to whitelist items in the programdata folder when that option is enabled. In most cases users will not need to whitelist items in the programdata, or appdata folder. That's not the case with WSA though.

 

Cool, well, if it happens again, you might try to delete the hidden shelliconcache file in the desktop folder... I did not think of this until just a few minutes ago. Just a thought!

 

Yeah, exactly, that is the thing, executables in appdata or programdata should not be whitelisted, but sometimes certain programs run child processes from these folders, even though they probably should not, that is why they are called appDATA and programDATA. Besides, as we all know, these are viruses and malwares favorite hangouts.

Although, I have to admit, VS downloads the new VS installer to C:\ProgramData\VoodooShield when it performs and update. I think I will change it to C:\Program Files\Common Files\VoodooShield.

Also, I think it is an easy fix to allow items in these folders when that option is checked. I will check it out. Thank you!

 

im an idiot disregard please. I forgot i was on another PC

 

I usually disable VS when installing software, or use install mode. In the case with some applications like WSA doing so many executions from the programdata, and appdata folder it's hard to know when those executions will begin to occur. WSA does so many that it's like a new install that happens at random, and who knows when it will occur. The user may not even be at their machine. I'm sure you will come up with something to accommodate this. I will try training mode next time if i'm at my machine, and maybe it will be painless from then on. I hope so anyways.