VoodooShield/Cyberlock

Hi Dan

Just to let you know that .73 is working great here on both Win7 64bit & Win8.1 32bit...and the new "Auto Immune" (my name for the Scan & Allow feature ) seems to work like a dream...my new favouritest bit of VS.

Will keep you posted if I do happen to come across anything during the testing.

Regards, Baldrick

 

Cool, thank you! Yeah, that was the whole point of 2.73... I tried to make it as efficient as possible, and tried to bug the user as little as possible, while still keeping everything secure.

 

Cool, thank you siketa and Baldrick!

 

I think everything is just right in the latest version, but if not, please let me know!

 

Cool, thank you for the suggestions. As you can see, I added about half of these in the latest version, and I will look into the other ones that have not yet been added.

 

Yeah, it should be fixed now, if not, please let me know!

 

Yeah, there really is not a lot of info we can gather on command line blocks. I might be able to add them to the user log though.

 

Yeah, but if a web app is running, these need to be blacklisted. I really do not see any way around this.

 

Cool, thank you, it should be fixed in the latest version, if not, please let me know.

 

Hmmm, that is odd. Please let me know if this is still an issue in the latest version... I bet it is fixed.

 

Hehehe, thank you Baldrick (and the other people with nice comments). So what do you think of the latest version?

 

Hi Dan...
2.73 on board and some strange behaviour - the module "Custom folders/custom blocked folders"...files in folders included inside should be automatically blocked and they are blocked...but not all. There are blocked files like "exe", "msi" - executable in general as I mean - but files like DOC, XLS, JPG can be executed without reaction of VS.
Is it bug or feature?

 

You have not yet gotten to that post yet, as I am sure that you have a lot of them to catch up on...

All I would say is that VS is now even more of a masterpiece than it was...can it get any better?

Baldrick

 

Hmmm, I am not sure, but VS disables UAC just as the user would, so really it has nothing to do with VS. Usually it is the other way around... usually it is UAC that causes issues... I see it ALL the time, especially with a lot of medical and dental software. It is quite funny when I am at a clients office and the medical software company remotes in to a computer to fix an issue, hehehe, the first thing they do EVERY TIME is to check to make sure UAC is disabled.

BTW, VS no longer prompts to disable UAC on installation. I figured that since UAC is disabled on 91% of all computers anyway, there is no need for VS to disable UAC... that way I do not have to hear about how disabling UAC is not a good idea .

Speaking of UAC, you guys might find this interesting .

http://blog.cylance.com/trick-me-once-shameonuac

 

Hi Dan,
Good to see you back with us (I know you've been busy).
I've just installed 2.73b and no problems so far. Seems to be running just great.

Many thanks
Gordon

 

Yeah, I agree. Currently, VS does not do anything with elevation of privileges... and if you ask me, that is an extremely old unix technology that should have been buried a lot time ago .

 

Cool, thank you for letting me know. This should be fixed in the latest version.

 

Hmmm, I am not sure... mainly because there is not a lot of information to be captured. Can you help me think of what kinds of info could be captured? If so, I can look into it, thank you!

 

Yeah, that should definitely be fixed in the latest version, if not, please let me know!

 

Thanks again guys for all of the nice comments! I would reply to each one individually, but that would take up too much space on this thread. Instead, how about I buy you guys a beer in Vegas soon? .

 

The blacklist items feature should be working correctly now, but if not, please let me know!

 

Cool, the other items should be fixed... but this one we need to think about: "Once set password, the only way to revert back to not using a password is to select "Set Password" with empty password fields. This is not intuitive." I agree, it is not intuitive... should we have a clear password button as well?

 

Yeah, it should be fixed in the latest version... it was kind of difficult to get it to work exactly the way we wanted to, but I think it is good now. If not, please let me know, thank you!

 

Yeah, this should FOR SURE be fixed in the latest version, if not, please let me know.

 

Cool, thank you for finding these bugs. I think they are all fixed in the latest version, if not, please let me know!