VoodooShield/Cyberlock

I will check it, thanks

 

I am workimg on it now. Planned for the next release

 

Hi Vlad

That sounds like good news...looking forward to it.

Regards, Baldrick

 

Still having issues with our old friend rundll32.exe

Daniel

 

Are you talking about synproc (WSA) issue?

 

That's weird. What is the command line?

Thanks

 

So looks like the issue that I fixed is not the same as you see (as I said I wasn't unable to reproduce it). I will think about some kind of engineering version of VS that will have more prints/details so I could know what's wrong there.

Do you still see the issue that after a clicking the notification no prompt is shown?

 

Are you talking about asking for netsh command?

 

The message about the digital signature is ok:

 

I think I'm missing what is the issue.
Please send me the log with the bug and the description of the issue, that includes:
- What are you doing
- What do you expect to see
- What do you actually see

Thanks in advance

 

Thanks
I see what's going on there.
The process nircmd.exe is whitelisted and running without prompt, however nircmd.exe starts cmd.exe, that is defined as blacked list application. So cmd.exe is never added to a whitelist. Currently it is the design of VS.

I think there might be a bug, that cmd.exe is not allowed automatically by parent process (nircmd.exe). I will check the issue when I'll have the access to my computer and will let you know.

Thanks a lot!

 

It is much safer if user can white-list the command line only - as opposed to applying parent process (nircmd.exe) trusted status to child process (cmd.exe).

I keep pointing this out. For optimum security, user must have option to manually white-list command line (and not process) and use wild-cards (to fix CL repeats - e.g. WSA sysprop). For example, in NVT ERP, just substitute (*) for process ID. Problem resolved in less than 30 seconds.

 

In this specific case nircmd.exe starts cmd.exe without any parameters, so the whitelisting the command line cannot be applied here. So currently it works as expected.

Fixed already

Wildcard is implemented already. The editing of it is not as user-friendly as I want, but I'm working on it.

 

Not wanting to spoil everyone's fun/party but I'm curious when we might expect the digitally signed 'Final Release' of version 3

 

As usual when it's ready. Also it's continuing to be updated even after the final comes out as things change over time which is a good thing.

Daniel

 

3.04beta working great. no longer have Webroot issue when launching IE

 

VS has been asking me to register a few times after I have already done so. It is also uploading white lists for 2 PC's but i only have 1 using VS.

 

Kill both VS processes and delete all in C:\ProgramData\VoodooShield and then go to your account and delete all PC's listed. https://voodooshield.com/ then reboot and register and that should do it.

Daniel

 

TY Helix ill try that again but im skeptical

 

Hi everyone! Vlad wanted me to post the latest version.

www.voodooshield.com/Download/beta3/InstallVoodooShield.exe

Release notes:

- Fix for the updating from the GUI
- Command line prompt fix
- Custom folders enablement
- Remove allow windows store option

Vlad also made a lot of changes to the Custom Folders option. There are a lot of different ways we can handle things in this option, so please let us know what you think! Obviously, we would like to make it as user friendly as possible.

I believe the last bug is the heap corruption bug from the service on Windows 7, if there are other bugs, please let us know!

On the heap corruption bug… how many users are experiencing this bug? Also, if you disable the option “Start VoodooShield when I start Windows” in the GUI, so that the GUI does not start on windows startup… then reboot your computer, does this issue still exist?

Please let me know and we will fix this last bug asap! Thank you!

 

Hi Dan,
Yes I am that man ! which is why I rolled my version back to 2.86. I believe Paulderdash also suffers with this bug.
I will have to reinstall v3 to be able to tell you if it still occurs or not. So i will install the newest version and let you know in due course.

Gordon

 

Hi Dan

Thanks for the heads up. Now installed (over the top) under Windows 10 64bit...and I will be looking forward to giving it a run through later this evening. Will feed back if I spot anything untoward. Will update my Windows 10 32bit tablet installation later on.

Regards, Baldrick

 

The bug with auto update still exists in 3.04,so this is why you see it. It should be fixed in 3.05 so the future update to 3.06 should work fine

 

Hi Dan, Vlad,
Uninstalled VS 2.86. Installed VS 3.05beta and disabled “Start VoodooShield when I start Windows” in the GUI.
Sorry to disappoint but the problem persists and slows down booting up due to all the error reporting. Re installed VS 2.86.

Regards
Gordon

 

Hi Vlad / Dan

Installations under Win 10 64bit & 32bit running well here.

Regards, Baldrick