VoodooShield/Cyberlock

Yeah, you can already click on the results, and it will automatically google that threat... it should be working in your current version. Although, we are unable to list which engines detected the threat.

 

I think a small button would suffice.

 

I'm not getting any option to click on in order to Google the results. I just checked. The only thing i'm getting is Block, and Quarantine. It also tells me what the threat is called.

 

Sounds good on the button. Yeah, if you just click on the actual threat (in blue italics), it should google that threat automatically in your default browser. I added that a long time ago, but forgot to tell everyone about it .

Here is the latest version. I was going to test a little more, but I tested throughout the weekend, and it seems to be super stable. I will double check to make sure the link is right too . Thank you!

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.05.exe

 

Disregard, Dan. I just clicked on the name of the threat, and it took me to Google. I think you need to make the threat name appear as a link. It just looks like regular text so I don't think anyone new to VS will know they can click on the threat name to Google it. I would highlight it in blue like a link.

 

I just checked again. The problem is that the mouse cursor does not change when you hover the cursor over the threat name. It just appears like regular text even though it is a blue color. Try hovering your mouse cursor over a link, and watch how the cursor changes depending on your cursor settings. Then try covering your cursor over the threat name on the VS prompt. It reacts like it is regular text, and not a link. Can that be changed? That's why I had no ideal I could Google the results.

 

Thanks, I will try the new build later this evening. I have to step out in a moment for lunch. I haven't eaten yet today.

 

Another option that just occurred to me is that you could just put a "click here for more information" at the end of the threat name. Have it appear as a hyper link. No one would overlook it then. Well, got to go grab some grub. Starving. Be back later this evening.

 

I terminated VoodoodShlieldSevice.exe and I just deleted all 5 so did the re-registering and rebooted and it came on so I will let you know how it goes from here!

Thanks,

Daniel

 

I'm still having the same issue with the Web Apps tab. As soon as it populates the list of applications to choose from to trigger Smart Mode VS freezes. If I try switching to a different tab VS freezes, and will not respond. If VS has been running very long then VS will not recover, and VS has to be killed. Maybe if I understood what VS does to detect the applications then maybe I could discover where the conflict is. I'm using a Netgear N600 Dual Band USB adapter with Windows 7X64 Ultimate. Is anyone else using VS with NOD 32, or Eset Smart Security? Maybe there is a conflict.

 

Sorry, things are a little crazy right now, but I will be back in a few days! I hope to have the last couple of bugs fixed as well. Thank you!

 

working so well

 

Cool, thank you guys!

Here is the latest version, I believe all of the issues are fixed, if not please let me know! I tried several different things with the web apps tab... but this version seemed to work the best. We can always expand on the web apps and sandboxing (along with other things).

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.07.exe

 

I just started getting this blocked by VS...

Spoiler: Screenshot

 

Cool, thank you for letting me know. I made several changes for Windows XP in the 2.07 version, so there might be a few little bugs like this.

Did VS display a balloon when this happened? What mode were you in? Was VS ON or OFF? I am going to bed now, but I will check back in the am. Thank you!

 

VoodooShield 2.0 ChangeLog

After almost a year in development, here are most of the new features in VoodooShield 2.0.

- VoodooShield 2.0 now offers a completely free, somewhat feature limited version, for non-commercial users. All of the vital functions are included in the free version, while VoodooShield Pro is geared more towards the corporate market, with options to manage all of the computers in your account and copy whitelist snapshots from one computer to any or all of the other computers in your account

- Changed the method for detecting and denying new processes from being created

- VoodooShield is now a true multi-threaded application, so it can block multiple processes at one time, without any user intervention at all

- Added sqlite for all of VoodooShield’s databases

- Added local settings that reads from the sqlite databases on startup to improve performance

- Added the VoodooShieldService, which allows VoodooShield to do a lot more than it could before

- Removed the “Scan with VirusTotal button” and replaced it with an automatic upload of all blocked files to the multiple scan engines

- Added a feature to automatically run new processes if a threat is not detected by the multiple scan engines

- Fixed the drag and drop to shield for virus scan so that it works on all operating systems

- Added a quarantine feature that isolates detected threats

- Added a Sandboxing button so the user can choose to run a blocked and scanned (non-installer) file with limited rights. We will expand on this feature even more in the future.

- Added a feature that temporarily allows unknown process by Publisher / Digital signature from the previously allowed executable

- Added a tab is settings to make it easy for users to decide which web apps should toggle VoodooShield in Smart Mode. Web apps are automatically detected as they communicate with the internet.

- Added “Custom Blocked Folders” so users can choose specific folders that are always initially denied

- Added local Backup and Restore of VoodooShield Settings and Whitelist Snapshot

- Added a Commands tab in Settings so users can manage executables with command lines

- Added a special algorithm that calculates the probability that the path is the intended path, without having to resort to wildcards, assuming that the process name and hash compare correctly

- Added local editing of the whitelist that syncs with the cloud whitelist

- Updated the prompts, which now are displayed in the bottom right hand corner, and help guide the user to make the correct decision on whether to allow something or not

- Added a Mini Prompt to notify the user what VoodooShield is up to

- Updated and tweaked all of VoodooShields screens / windows

- Fixed the notorious bug in VoodooShield 1.30 that would appear when another thread was trying to access the Desktop Shield graphic

- Automatic importing of account information from VoodooShield 1.30

- Automatic dismissal of kernel messages when VoodooShield blocks a process

- Added logs

 

Great! Thank you! Btw, why there's no link for VoodooShield 2.0 on the download page?
http://voodooshield.com/Download/

 

working great

 

Cool, thank you PaullBB and MrGump! I am going to wait a couple more days before posting a link on the download page. I wanted to look at the XP issue that Tarnak found, and also make sure there is nothing else we need to fix . It will be a lot easier to make sure all of the bugs are fixed before we release 2.0 to the public.

 

Are you sure it's better than v2.05th?

Daniel

 

Hehehe, it should be, except unfortunately I had to drop the letters TH . It should be just like the TH version, except I fixed the web apps tab, and tweaked some XP stuff. But if anything changed, please let me know! Thank you!

 

Hi Dan

Will get this installed on into the testing program...will get back to you with an update as soon as I have put some miles on the clock.

Regards, Baldrick

 

Ok, this bug is fixed, along with another small bug with the 5 minute OFF warning. Since it was only 7 lines of code total, I just kept it 2.07.

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.07.exe

BTW, about XP... I have been meaning to explain the whole deal with XP a little better. We definitely need to do our best to support XP, since it looks like it is going to be around for awhile. But there are certain things that we cannot do with XP that we can do for Vista and above, and we definitely do not want XP holding back VS from using the newer and better methods, so there is kind of a balancing act we have to figure out. For example, under Settings / Tweaks / "Do not whitelist the following items" does not work nearly as well in XP as it does in Vista and above. For XP, these items must be blacklisted when VS is ON (unless the user chooses otherwise). With Vista and above, VS can whitelist specific command lines, so we can do some pretty cool things with this that are perfectly safe.

The kernel mode driver for VS is on hold temporarily. Our new developer worked really hard and got really far with the kmd, and then realized that it was not going to work with XP, so he is going to take a break for awhile and we will figure it out once he is well rested . The main reason we started developing a kmd was because I initially thought that it would make it possible to do everything in XP that we can do for Vista and above, but it does not look like that is the case. There are a few different methods we can use to develop a kmd... the older one(s) that works with XP is great, but it is not quite as advanced as the newer ones that only work for Vista and above. And as I was saying, I really do not want XP to hold VS back, especially since XP is 12 years old . In my opinion, the kmd is not vital, but it would be nice to have that option.

Also, I wanted to explain one other thing. When we first started developing VS 2.0, our overall approach could have been either a). allow everything, and figure out what to block, or b). block everything, and figure out what to allow. We decided to go with option b, which is in my opinion the better and more secure approach, but much more difficult during development (eg. silent blocking issues ). It was a major struggle for everyone involved (obviously including you guys), but somehow we got through it!

Thanks again for all of your help!

 

Cool, thank you!

 

I just updated from VS 2.05 to the second build of 2.07. I uninstalled 2.05, and installed 2.07 without removing any orphaned files from previous installations. I definitely like the changes that were made to the web apps tab. I hope this resolves the freezing problem I have been experiencing with the web apps tab. I will report back if I run into any issues. I may start throwing some malware at it soon.