Discussion in 'other anti-malware software' started by CloneRanger, Dec 7, 2011.
I think the answer to who is MOST responsible has to be A.
I would have to go with A. As a business owner I don't have much control over B,C,D with the companies I do business with, only myself. That's why as a small business owner I assume it to be my total responsibility to protect my clients data. It's not easy, but totally necessary in my book
Yes, works perfectly now! Thank you. I'm looking forward to tomorrow's new version with the freeze issue hopefully fixed. I haven't had the current beta on the system long enough to test whether it's going to freeze or not just yet.
I assume that voodoo AI is still disabled?
Thank you guys for your kind words (and your patients )... I will catch up soon, but I wanted to post the latest version, I believe the freeze issue is finally fixed. If for some reason it is not, please disable VoodooAi and see if it freezes, and please let me know either way, thank you!
We might disagree on some things, but I absolutely respect your efforts to protect your clients data
How does one disable VoodooAI.
You can disable VoodooAi in Settings / Advanced... it is the last option on that tab.
BTW... this is really odd... I just tried to install VS 3.33 on my Windows 7 computer, and for some reason, it does not like the driver to be signed by Microsoft, so VS does not start... it says "VoodooShield failed to initialize one of the required components...". But when I use the old driver, it works just great.
So something is very odd with this, and it will be an easy fix, but I was just curious if anyone else has had this issue.
Edit: It probably has to do with my machine not being updated in a long time, and it probably does not understand the new EV signature. There are several workarounds for this, but I just have to figure out which one makes the most sense. Anyway, if anyone knows about this (like WildByDesign), please let me know!
A. My contract is with you, and I trusted you (Mr/Mrs/Ms Business). You can pass on the grief to your suppliers who let you down. Pass the parcel time. But as soon as the lawyers appear we all acquire a dose of common-sense.
Installed VS 3.33 Beta and there's no problem with the driver. There was a driver signature problem with an earlier version of VS but I have driver signature enforcement disabled anyway.
Here's what I see currently.
Just installed 3.33 on my Win 7 Pro and all went smoothly with the new signed driver. So it is perhaps just your machine Dan.
A > D > C > B
BTW, the whole digital signature thing should be fixed, so VS 3.33 should be good to go... I just uploaded a correctly signed version, so if anyone had issues, please try to download again, thank you!
Sorry to say but I've just experienced a complete lockup of this PC after installing v333. It seems to have happened while VS & Cuckoo were examining a legit Onenote addon that I was trying to open here.
Log files sent.
EDIT. Locked up this PCsolidly after a reboot. No progs running apart from the regular start up services and progs. Uninstalled for now.
On top of everything is "The Company you deal with" they are in deal with you, not the authors of software they use ( security or busines software ), you have nothing with OS they running,security software they use or any other software they use!
"The Company you deal with" must be responsible for the damage you have and later they will sue the software company who is responsible to them bcz they "have deal" with that software company!
That is my opinion.
BTW: I don't have PRO licence to explore things under settings but free version does not show's blocked threats in quarantine and it would be nice that we have option to install VS to another location
Just had another freeze with 332. As always it happens after installing a program.
Now installed 333 and will see how that goes.
Thank you for letting me know... I am hoping and assuming that this is a coincidence / fluke, because as far as I know, VS had never locked up a system or caused a BSOD. The freeze issue did not lock up the entire system, it just froze the VS gui. I do not think that the changes in 3.33 could possible cause any issues at all... basically the only changes were fixing the path if they started with "systemroot" instead of "c:", and it also checks the file to see if VS has read access to the file. What was the Onenote addon that VS was examining? What version of Windows are you running? Thank you!
Hey TH, here is a rundown. I am going to look at my to do list soon, and post a list of the final bugs / changes, and you guys can add anything I missed, thank you!
1. Freeze issue (most likely a privilege / permissions issue) (I think this is fixed)
2. guest's custom folder GUI bugs (fixed)
3. Chrome update issue / Blacklist showing unknown file (I am not sure if this is fixed or not... if it happens with 3.33, please let me know!)
4. Dismhost bug (fixed)
5. Fix Disable/Install Mode so it works as it should. (fixed)
6. USB Mode has it been fixed to be ON whenever a USB device has been inserted no matter what? (we discussed this)
Thank you TonyW... I just added those to my to do list and will look at them again soon!
Thank you shmu26... there is a new feature in 3.33 that should fix the hp printer issue, and hopefully the logitech as well. If not, please let me know!
The thing is... the way vulnerable processes are handled in VS is really the best of both worlds. It is hard to explain, but a while back, I made it so that every executable file in windows was considered a vulnerable process (along with the other standard vulnerable processes, like java and flash), and these vulnerable process are only blocked when they are child processes of web apps. Also, keep in mind, this applies to all windows processes, and every few months a "new vulnerable process" is "discovered", so we do not have to constantly update the vulnerable process list, since all windows files (along with the standard vulnerable processes) are considered to be vulnerable.
Having said that, if you can find an item that VS blocks, or basically show me that something is not working correctly with the way VS is currently automatically handling all vulnerable process, please let me know and we can tweak it, or add a customizable vulnerable process list. But really, not only is this method more secure, it is fully automated and drastically reduces the number of items that should not be blocked in first place, since the vulnerable processes only apply to web apps. I hope this makes sense, if not, please let me know!
That is really odd... what logitech software are you using? I will have to install it and see... there is no reason that I can see why VS would not whitelist that item. Also, please try 3.33 and see if this item is still blocked. Thank you!
Please see https://www.wilderssecurity.com/threads/voodooshield.313706/page-478#post-2611657 and let me know what you think! Thank you!
Great to hear, thank you! BTW, I THINK all of the driver signing issues are completely fixed... if not, please let me know. It turns out, Windows 7 does not like the EV certificates... so basically for Vista and 7, the driver is signed in the traditional way, but for 8 and above, the new signature is used. It took a while to figure all of that out, but we are good to go now. Basically, during the VS install, the appropriately signed driver will be installed for each windows version.