VoodooShield/Cyberlock

Yes, like for example, if you try to install a .msi file, VS should just flash once. This will change once the cmd / msi issue is fixed. In the end, hopefully it will all work perfectly and make sense .

 

I am currently on 1.26.1. Cannot d/l 1.26.2 - is it still available?

On the USB issue. At the moment non of the USB devices are switched on yes the USB icon is showing and prior to that VS popped up asking the question. I have a feeling that VS is thinking my SSD is a USB. Thought that the other day when I first installed it. Anyone else noticed this?

 

Still works for me! https://voodooshield.com/freeoffer/Install VoodooShield.1.26.2.exe

Daniel

 

working very well for me

 

Now it does - Thanks

 

Way back at #1008 I posted about a conflict with VoodooShield, Chrome and Sandboxie. It turned out to be a drop rights issue that went away when that setting was unchecked in Sandboxie. I've just re-installed VS and am still seeing the problem, so it hasn't been fixed in VS or Sandboxie. I've again unchecked drop rights, and the problem has again gone away. Does VS give the same protection that drop rights was in Sandboxie? If not, is there some other lightweight program that can cover that?

I've installed VS again because I was told that a slowdown I'm experiencing when opening programs can be caused by UAC. VS turns off UAC and I hope is giving similar or better protection than UAC. Does VS respond faster than UAC when starting up programs?

 

Is the way that VoodooShield works similar to Faronics Anti-Executable?

 

I think I fixed this in 1.26.2, but if not, please let me know. The computer I am on now has a small SSD for the C drive and it works fine. Is your SSD your primary drive too? Thank you!

 

I just installed VS 1.26.2 on my test image, and after rebooting the tray icon did not load. VS desktop shield gadget loaded, but not the tray icon. Shutting down VS, and restarting it made the tray icon load.

 

I am not very familiar with SB, I think it is a great program, I just haven't had time to use it that much. So I am not familiar with what drop rights does. From what I understand, SB might issue some dos commands that VS blocks, but that will be fixed soon. Hopefully someone who uses both SB and VS can answer your question better than I can.

As far as UAC goes, it really is not designed to stop viruses and malware, and it turns out, it doesn't. I always find it ironic when I am removing a virus from a client's computer, and UAC is blocking the cleanup and virus removal utilities that I am trying to install to remove the virus.

UAC does respond a touch faster since it is buried so deep into windows, but if it doesn't respond at all, then I guess you could say VS is faster . But yes, I am sure VS provides much better protection than UAC.

 

I probably should not comment since I am biased, but here is a very good comparative review .

http://www.pcmag.com/article2/0,2817,2422274,00.asp

 

Thank you for letting me know. I cleaned up the icon code really well in 1.26, it was all over the place, now it is all in one spot. I will double check right now to make sure the tray icon is initialized properly.

 

I just tried running the latest installer for Tinywall from Users/user/downloads, and also from the desktop. VS blocked it without giving me an option to allow it. The tray icon flashed upon executing the installer, but it did not give an option to allow or deny the installer. I tried to execute the installer while in Smart Mode, and Always On Mode from Users/user/downloads, and the desktop. I tried to execute the installer 7 times, and each time VS tray icon flashed without giving me an option to allow or deny it. The log file says VS blocked msiexec for each time I attempted to run the installer.

I believe expected behavior should give the user so many seconds to allow or deny the installer. That has been the behavior of VS in previous builds.

You can download Tinywall's installer from here, and test it for your self http://tinywall.pados.hu/

 

No problem! I enjoy using VS.

 

Yes, right now VS is blocking .msi files and not prompting the user, since it would try to run the path that is shown in your user log, which would not run the TinyWall installer, it would just run msiexec. So until the cmd / msi issue is fixed, we just make VS flash once, and not prompt the user, since VS cannot find the path of the original file until this is fixed. I hope that makes sense! This applies to any cmd and msi file.

 

Thank you.

 

I understand what you are saying, but I could have sworn I've executed some msi files recently, and VS prompted me. I could be wrong. If I do come across one that causes VS to give me an option to allow or deny the msi then I will let you know. Maybe it was a different type of installer.

 

Before we implemented the blacklisting, it might have prompted the user, but that has been a year and a half or so. It is hard to say, but it must have been a different installer. I found an installer the other day that started out as an exe, then changed to an msi... very weird.

 

I went back, and checked some of the ones that prompted me, and they were exe files. I was mistaken.

 

Good deal, thank you for letting me know.

Ok, here is a version that should have all of the prompts working perfectly. The Virus Total uploader is a lot smoother now. I will turn off the animated uploading graphic once the file is uploaded, I just do not have time tonight. The icons a tray icons should be working perfectly too.

If there are any issues, please let me know!

https://voodooshield.com/freeoffer/Install VoodooShield.1.26.3.exe

 

Yes it is. This morning it is not showing USB icon with 1.26.2 so hopefully you fixed it

Thanks

 

No problem with v1.26.3

 

Just installed 1.26.3 no reboot.

Been playing with a program http://en.pdf24.org/ and went to uninstall it and VS popped up. Clicked allow and nothing happened. Clicked Block and it allowed the progress to proceed. I am in Smart Mode and the icon changed to Off although I was using the browser. Now suddenly it has changed to On. Some weirdness going on.

 

You always have to do a reboot when installing or updating VS to set the new updated code.

Daniel

 

Cool, thank you for the feedback!