VoodooShield/Cyberlock

No apparent problems on running and rebooting on two machines with 354beta, and now 354Krusty2 on primary machine.

 

It has to be allowed by VS so is possible. The file will be scanned in VT as usual but VS will only consider the engines you select for the calculations


New version is working fine here

 

Reverted to 3.53
All issues gone.

 

Same for me as my computer would not boot last night. With 3.53 no problems.

 

I meant, as per VT policy, you kinda cannot have the option to select engines for detection.......i.e you have to use all the engines for detection.

I too had proposed engine selection to Dan & Kardo (Crystal Security)...........Kardo mentioned kinda violates VT policy.

I like VAi & would love to use Standalone VAi.

 

3.54 running ok here on 8.1/64. Will try the latest Krusty version now.

 

Installed the 354 Krusty2 edition. Seems fine with restart/shutdown/startup. Very fast startup for VoodooShield. I think I'll disable it when next month's Windows updates roll around. But so far, so good. Windows 10 14393.953.

 

InstallVoodooShield354Krusty2 installed and all seems good here.

 

You guys probably already know this, but if for you are running the latest beta version of VS, and the screen hangs on login, just hit ctrl+alt+del and kill VoodooShieldService and VoodooShield, then logout and log back in. After that, you can just uninstall the beta version for now, until the new self-protection feature bugs are fixed. I figured this would be a pain to implement, but we are getting close, thank you!

 

Dan which version would you like to go back to 3.53?

Also I assume I got this because it was unsigned?

 

Yeah, everyone please hold off for a couple of hours on installing 3.54... I think all of the self-protection bugs are fixed, but I am going to test for a couple of hours to make sure. Thank you, sorry for the inconvenience!

 

Yeah, everyone should go back to 3.53 for now... I am not sure about the prompt, I will have to look at it. The digital signature alone does not determine whether a file will be blocked or not. For example, there are plenty of files that are not signed, that are auto-allowed by the blacklist and VoodooAi in Smart Mode (when VS is OFF, no web apps running) or Always ON mode. The digital signature that is displayed on the user prompt really is for informational purposes only. The digital signature does have some weight in determining maliciousness with VoodooAi, but it is only one (well, actually 20 or so) of 400 or so factors.

 

I know, but what I requested has nothing to do with disabling engines in VT.

 

OK, installed the last 3.53 over the 3.54 Krusty2 and am anticipating the changes to the latest version. Wonder what causes 3.54 not to work for some and work for others? Specifically with startup/restart?

 

Dan - is it OK to just install 3.53 over 3.54Krusty2?

 

Yeah, you should be able to just install over the top... the reason it works for some and not others is because of different OS's and different actions as far as Restart / Shutdown / Log ON / Switch user. It really is not hard to fix... I just have to go through each scenario on each OS and make sure everything that should be allowed is allowed, and everything that should be blocked is blocked .

 

Rgr that boss
Rolling back.....

 

Yes also. I am having some issues with latest Windows Updates and want to eliminate that VS 354 has something to do with it (even when set on disable / install).

 

Hi @VoodooShield

Def not a high priority but can I suggest that you add release notes in the VS webpage for each version?

Thanks

 

Hey guys, sorry this is taking so long... I just want to make sure I get this right, so it is less of a pain for you when you try the new version . Getting close!

I have tons of emails and pm's from the last week or so that I will respond to asap... sorry about that too.

Once 3.55 is ready, things will not be so crazy .

 

Ok thank you. And can you please check out sticky password on your pc plz because it allows it first instance they later down blocks it (browser ext) puzzled.

https://www.stickypassword.com/help/download

 

Looking forward to test it. Thanks Dan for your hard work.

 

No problems with Sticky Password here. Be sure to whitelist both...

c:\program files (x86)\sticky password\stpass.exe
c:\program files (x86)\sticky password\spnmhost.exe

Updating SP will require you to whitelist both updated executables.

I also see 2 command line entries for SP...
(there may be typos here )
c:\program files (x86)\sticky password\spnmhost.exe chrome-extension2//kaafoaobjaplofpihlhbcbcjhmgnjplfl —parentwindow=O \\.\pipe\chromenativemessagingjn.7bda6367ffd21c5O \\.\pipe\chromenativemessagingout.7bda6367ffd21c5O

"c:\program files (x86)\sticky password\stpass.exe" -showcaptionbuttonmenuwnd=66594

 

I too used Sticky & VS in the past and Telos is correct white list
them both to prevent issues.