VoodooShield

[ichito]

Nowa wersja ze sporą ilością zmian

Kod:

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.31 beta.exe

Opis do tej wersji poniżej

Kod:

Hey everyone, I will reply to the above posts a little later. I was a very productive weekend, and I added a lot of new stuff. And I also installed the new version of Visual Studio 2013 Ultimate, and it found almost 200 "bugs", although most were just optimizations. I have all but 16 fixed ;). I will fix the other 16 this week, but seriously, they are no big deal at all. But, there were A LOT of changes under the hood, so please let me know if VS does something odd.

Here is what I added:

- Fixed the targeted VoodooShield bypass (Basically just added self protection). I was always reluctant to add self protection in case something went wrong, but I figured out how to do it, and still allow the user to kill VS in the Task Manager if necessary. I am going to have to add another self protection mechanism as well, I will do that soon.

- Changed a few things in Settings

- Added a prompt 3 weeks after installation that asks the user if they would like to disable auto allow. You can move your clock forward 3-4 weeks and you should be able to test this prompt.

- Put the close X back in the User Prompt for TH ;)

- Put the Allow False Positive link back in the User Prompt. You can still turn the button on in Settings / advanced so you can have the full button if you like. CET will like this ;).

- VS is now 100% Windows 10 compatible (build 9926 and above)

- I also found new places in the registry to obtain a really great snapshot, wait until you see it in action! It is a combination of a couple of different things, but basically adds your recent / frequently used programs to the snapshot. I added the Take Snapshot right click option in full time so users can easily access this feature. Or you can reset your snapshot, or click on the Automatically allow all software from the Program Files folder option in settings to access this feature. Please keep in mind during testing... if you add the Extended Whitelist items, there is a HECK of a chance that any executables you are using to test will be automatically whitelisted. So for example, if you have a folder on your desktop with malware in it, and you use this new option, VS will whitelist the malware. But there is a prompt that addresses this issue... basically it asks if this is a new / clean computer, or one that has been recently infected. If the user clicks NO, then the standard snapshot is taken, and not the extended. Also, the extended snapshot is not currently set to add the new items to the user log, but it does add them to the snapshot. We can go either way on this, but I would prefer to just add them to the whitelist, but please let me know if you guys think we should log them in the user log as well. To me, the user log... well, is the user log and logs how the user interacts with VS. But we can go either way, just let me know what you guys think!

- Also, I am trying something new. There are a handful of troublesome windows processes, for example, dismhost.exe that would be blocked when Windows Disk Cleanup was started. I am going to specifically (and safely) whitelist these processes, basically hardwire them in like we do the standard command lines. So if anyone has a windows process that seems to be blocked all the time for no reason, please let me know. This is assuming that you have the auto allow specific critical windows processes enabled. Otherwsise, I cannot list them all ;).

- Fixed close to 200 "bugs" from Visual Studio Code Analysis... almost all were optimizations and security fixes

I meant to work on the change log for 2.30 and the instruction manual this weekend and today, but I kinda got carried away with adding new stuff. There are other small new features and optimizations as well.

[Aby zobaczyć linki, zarejestruj się tutaj]