VoodooShield/Cyberlock

Irrelevant to the discussion of the app itself but the web site and registration password system leaves a lot to be desired.

• Plain text password reminders transmitted insecurely via email.
• (no or limited?) special characters permitted in the password.
• Maximum password length not specified.

In this day and age with all the web site hacks recently, this should be addressed a.s.a.p. please guys.

 

@VoodooShield - Any possible way to add a right-click contextual menu in Windows Explorer, "Scan with VoodooShield"?

Sometimes I would rather much prefer a right-click contextual menu, rather than having VoodooShield scan (VirusTotal) when an executable is initiated.

 

restarted VS and it reverted back to unregistered, this is second time this has happened. once time with each of the last 2 releases .both times it was clean install

 

I just installed beta build 3.05, and I have not experienced any problems yet. I have not rebooted yet so we will see. I'm using Windows 7X64 Ultimate.

 

installed beta, looks good. Doesn't auto turn off UAC.

 

UAC hasn't been disabled for many versions now. I'm sure someone will correct me, but since at least v2.75, maybe earlier.

 

Ok I haven't tried it for awhile but everything seems smoother now.

 

@VoodooShield Isn't it a mistake for the "Auto allow by parent process" under the advanced tab to be checked? This is allowing any file to be executed if clicked on from the browser download page, whereas it won't auto allow if tried directly from the downloads folder. After I unchecked this option, it is working like the anti-executable that I want.

 

That is a bug unless your web browser is not listed in the Web Apps List. It should not be allowing executable to execute through your web browser if your web browser is on the Web Apps List. I always uncheck that option myself.

 

Was hoping to hear something about the Final Version Release.

 

It will take more time; no ETA. There are many issues - and not just the soft itself - like time delays, coordination between parties, etc, etc.

Those sort of things are inevitable and not a negative reflection in any way on VooDooShield and the developer.

 

Hello
There is a bug in 3.05, that the files started by the allowed browser are allowed automatically.
It is fixed and the fix will be released in the next release.

thanks

 

Those are good ideas that will improve the VS user experience.
I need to check with Dan so he could decide what and when to implement

thanks

 

Hi All

Just a quick update to say that v3.05 beta seems to be running really well here; Win 10 64bit Desktop system & Win 10 32bit Tablet system.

Have been cycling through some usability tests and so far have found nothing that screams out at me. I tend to keep both instances in Scan & Allow mode and it almost makes for silnet protection...just popping up if there is anything potentially untoward identified.

So far an excellent job.

Regards, Baldrick

 

@VoodooShield @VladimirM any new news?

Thanks,

Daniel

 

Kinda interesting, I've had VD shield version 2.75 installed for about 3 months and just today received 'in program update' to version 2.86
which I've been reading about for about 3 months.

 

I had one snapshot where I updated it, manually. Today, when I booted into the remaining snapshot which, also had VS installed, I got the popup that a new version was available. I had v2.79b installed in that snapshot, so I let it update to v2.86.

 

VoodooShield 3.06 Beta Release
You can download it from https://voodooshield.com/Download/beta3/InstallVoodooShield.exe

System requirements:

• Windows Vista sp1 and above (XP is not supported!)
• .NET 2.0/3.5 and above

What's new in VoodooShield 3.06 Beta:

This release contains the fixes for the following bugs

• Starting application from some browsers download window is allowed
• Showing propmt for applications started from the Start menu freezes on the shield flashing (win
• After ~30 days of working the auto-deactivation feature becomes unavailable
• Starting cmd.exe only shows prompt for command line, rather than for blacked list item

Known issues

• Windows 7 - VoodooShieldService.exe crashes on Windows restart. Impact - fills event log with crash events + crash dumps. Still under investigation

Have a good day,
Vladimir

 

Thanks Vlad. I'm still hoping you can sort out the issue in Win 7 eventually.
Gordon

 

All well installed here...via the internal updater. And seems to be running fine here.

Regards, Baldrick

 

Any ETA on when the next build will be released? Are many users experiencing the VS crash mentioned for Windows 7? I used it for a short time, and did not experience any crash.

 

It's working great on Windows 10 x64.

Daniel

 

Absolutely...working like a charm on Win 10 Pro & Home.

Baldrick

 

I'm using Windows 7X64, and that's were the problem was reported. I only used the KMD version of VS for a couple of days, and did not have VS crash.

 

Sorry I have been away…. VoodooAi has taken a little longer than I initially expected, but it is almost ready. Then again, it has only been a couple of months, right .

While no method of malware detection is perfect… assuming the results continue to be as promising as currently are, I believe you guys will be as amazed as I am. VoodooAi is not intended to replace VoodooShield, but rather to compliment it and most importantly to detect the unknowns and zero days. Machine learning / Ai does not care if the file is a zero day or 10 years old… it does not know the difference. So basically, I believe the computer should still be locked whenever a web app is running, but if the user tries to run something that is not whitelisted, then the current 57 scan engine blacklist scan or VoodooAi will make sure that the user does not accidently allow something that should not be allowed.

I guess what I am saying is that Machine Learning and Ai, as accurate and precise as it is, it is NOT the end of malware… I believe locking your computer is the end of malware . We just have to make the lock as user-friendly as possible so that people will actually lock their computer.

I attached the machine learning model statistics as they stand now. Believe it or not, they will only get better. These numbers are based on a small sample set, and VoodooAi will only get smarter as files are analyzed with VoodooShield and added to the data set… not to mention the fact that I am going to add massive amounts of samples to the data set in a couple of days. I had to wait until all of the bugs were worked out before I wasted time uploaded massive amounts of samples. BTW, if you guys have clean or malware samples that we can upload in the next week or two, please let me know. Believe it or not, I have found that it is more difficult to find massive amounts of clean samples than malware, since malware packs exist, but I have yet to find a repository for clean files. Please let me know if you can help!

BTW, these statistics are automatically generated when the machine learning model is built. Basically, a small percentage of the samples (5% or so) are excluded from the model training and are actually tested against the model for accuracy and precision, so that you will know if your model is working or not. It took a while to get it right, but I finally did. At some point I will probably hire a data scientist to tweak my models even more… I will be curious to see the results .

Also... this is really cool. As I upload samples to the sample set, commonly used safe files such as “Windows” and “Program Files” files will be marked as “Default Processes” so that when VS blocks one of these files, it will automatically be allowed. The goal is not to create a massive whitelist of every file in the wild (you might as well just create a massive blacklist ), but for all of the common files that are known to be absolutely safe, like right after you install Windows and Office (along with a few others) on a clean system, these will all be automatically allowed by VS. However, we do have the capability to auto whitelist anything that comes back as 0/57 from the blacklist, for all VS users (after the file is initially analyzed by the first user). Thankfully we included this in our patent 4.5 years ago, which btw was granted on November 24th!

Vlad is still working on the last VS 3.0 Windows 7 heap bug… I wish I could help him, but he will be able to solve the issue much better than I can. I have offered a few suggestions, but I am certain that they are things that he has probably already thought of. Once he is finished with that, I am hoping that he has time to help me with a couple of last issues that I am having with VoodooAi. I will probably release a demo version of VoodooAi soon so you guys can take a look… and obviously it will be integrated into VS soon too.

Happy holidays everyone, I hope to talk to you soon! And as always, thank you for your support!

http://voodooshield.com/artwork/VoodooAi1.png

http://voodooshield.com/artwork/VoodooAi2.png