VoodooShield/Cyberlock

Regarding the manual or automatic methods i would have the automatic as default for the less security savvy.
and the manual check box (which switches auto off) available for us more security conscious users in the preferences.

 

Ok, you have plenty of ~ Snipped ~ (not expecting friends) with regards to VD..however:

I love VD actually, but i are you going to get rid off the requirement for .net 3.5 or are this just talk again ...OK, not making friends by now but you talk A LOT.

No ~ Snipped as per TOS ~, please just brutal honesty please, i'm never going to install Voodooshield on 8.1 or 10 requiring 3.5 for that matter, i love the application though (VD) and are absolutely willing to test when that happens, hope my honesty is appreciated....but expect ~ Snipped ~ though....is there hope?

 

@Dan
2.20a beta flagged by VS 2.13beta

Mal/Generic-S ~ Suspicious_GEN.F47V1203

 

It's totally cool, it helps to discuss these things so that VS makes sense to everyone and works as excpected! Yeah, I see your point, VS should not toggle with a sandboxed web app... that makes perfect sense to me, thank you for the suggestion! But if someone is running a sandboxed web app, then runs a non-sandboxed web app, then VS should toggle with the non-sandboxed web app, right? Let me see what I can do, that might be a little tricky to implement, but that does make sense to me.

That quote on our website was from a long time ago, but I still would agree with it, especially after I make the changes to not toggle with sandboxed apps.

 

Yeah, I have been meaning to do that, I think the code is already written for that, I just need to implement it. Thank you!

 

Yeah, this is by far VS's biggest bug, and we need to fix it asap! It should be easy to fix now.

If anyone is having this issue, can you guys do me a huge favor? Please exit out of VS and delete the following files in these folders... if the service is running, it will only delete 4 of the 5, which is fine. Then, if the VoodooShield service does not start again at some point, please let me know.

Windows XP: C:\Documents and Settings\All Users\Application Data
Windows 7 and above: C:\ProgramData\VoodooShield

I used a really great method in 2.20a to install the service, so I thought it was fixed, so I do not want to make any unnecessary changes that could complicate things. If it still is not fixed, it should be easy to figure out because there are not too many more things it could be . If I could duplicate the bug on my system, it would help tremendously, but I have yet to see this bug. Thank you!

 

Sorry about that, it is fixed in the new version. Thank you for letting me know!

 

Hmmm, 2.20a should have installed the service as Automatic, I will have to double check that, thank you!

 

Cool, let me see what I can do on the Command Line feature, thank you!

On the colors, I agree, we need to find some really cool colors. I tried really hard to find the right colors, but I am really bad with colors . Please let me know if anyone has any suggestions!

 

Cool, thank you, that is kind of what I am thinking as well.

 

Hehehe, yeah, we are definitely going to have a native .net version of VS for all versions of Windows, well for Windows 7 and up anyway, possibly even Vista. From what I remember, XP did not have a native version of .net, so we will just go with 3.5 for it. The thing is, once we do this, every time we compile the installer, it is A LOT more work. But once we get VS where we want it, then yeah, I definitely want to do this. I would guess this should happen within the next 3 months or so, possibly sooner. Thank you!

 

Yeah, thank you for letting me know. I typically do not worry about the beta installers, but obviously for the public releases we need to make sure that there are no false positives.

 

I see what you are saying... I think pretty much all traditional AV software does MUCH more than simple blacklisting. The problem is... here is a quote from the Imperva report "The initial detection rate of a newly created virus is less than 5%. Although vendors try to update their detection mechanisms, the initial detection rate of new viruses is nearly zero. We believe that the majority of antivirus products on the market can’t keep up with the rate of virus propagation on the Internet." So while they have all kinds of methods to stop malware, the reality is, the initial detection rate for a newly created virus is less than 5%.

By no means am I bashing the AV industry... I think they are doing everything they can to fix this problem, and it is an EXTREMELY difficult fight for them. All I am saying is that I believe that the only way to fix this issue is to lock our computers. I think 5 years from now, we will all look back and say "can you believe there was a time that we did not lock our web connected devices." BTW, I am not suggesting that the only answer is VS... I am simply suggesting that the only answer is to lock our computers. And I would be MORE than happy if someone comes out with a perfect computer lock tomorrow that blows VS out of the water... that way I could get back to my normal life . But until that happens, I am going to keep trying to create the perfect computer lock.

So if Norton really does have something new that works really, really well, that is seriously great news! The thing is, I still believe that the ONLY way to solve this problem is to lock our computers. I first realized that May 5th, 2011 at 3:00 in the morning while I was removing viruses from 2 different client's laptops. I thought to myself "as bad as the malware situation is, there is just no way we are ever going to put an end to it unless we lock our computers.", and each day I am more and more convinced that this is true. Back then, there were 15,000 or so new threats a day, and now there are over 100,000 (depending on who you ask ).

 

Cool, thank you for letting me know! I see what the problem is, it should be an easy fix. VS is generating a new Machine ID whenever it was registered again. I hope to have that fixed soon!

 

Yeah, that is what I meant to say, thank you .

 

Yeah, that too!

 

I think the sandboxie thing is figured out, hopefully . We are just not going to toggle VS with a sandboxed web app.

The new version has an option to include the allow button for false positives, although this is disabled by default, since the vast majority of users are not security experts, and we want to keep them safe. Most pen test and similar executables are detect as malware, right? Thank you!

 

This is a bug, hopefully it is fixed in 2.20a!

 

You mean before EVERYTHING listed in your signature .

 

Cool, thank you, I will look into the conhost issue!

 

My God when I see the work you are putting to fine tune this application and the time you spent on this Forum to answer questions, by all means you deserve
the money I spent to buy Voodooshield.

 

In that case, it is probably easiest to right click on VS and choose Disable Protection. I am not a fan of the whole allow once concept (and I am not bashing any software that does include this option). The reason I say this is because, to me, computer security should be black and white, or basically binary. Either a file is allowed to run on your system, or it is NEVER allowed to run on your system (with the exception of running sandboxed after a blacklist scan of course ). When we venture into the grey area, that is when things become confusing and do not seem to work well, not that an Allow Once button would create an issue. I suppose we could add it at some point, but I really like to keep VS as simple as possible. Thank you for the suggestion though!

 

Thank you! Yeah, I am bad with colors and word tense's .

Please select the web apps you would like VoodooShield to toggle with and protect?

Actually, I can probably drop the "Protect" because VS does not technically protect the web app, it protects the computer.

Please let me know if you have any other suggestions on the verbiage, thank you!

 

Thank you everyone for all of your positive comments on the new GUI! Please let me know what colors you guys recommend!

 

Hehehe, siketa, you always crack me up! Thank you!