What Is New In madCodeHook 3.0

•  full support for 64bit OSs The complete functionality of madCodeHook now fully supports 32bit and 64bit processes on 32bit and 64bit OSs. •  safe driver based system wide DLL injection With madCodeHook 2.x every application using madCodeHook shared the same driver. This could create reliability issues and security issues (misuse by malware). With madCodeHook 3.x every application using madCodeHook has its own separate driver, which is always limited to inject only "known" DLLs, and which is signed by the application company's own certificate. This should protect the driver based injection from malware misuse. There's a new separate API set available now for controlling the madCodeHook 3.0 injection drivers. •  black & white lists for DLL injection System wide DLL injection can now be controlled by providing a black and/or white list. These lists can contain any numbers of exe file name paths/names. Wildcards ("?" and "*") are supported in both path and file name.

64bit Requirements & Limitations

•  madCodeHook 3.0 For feature complete 64bit support you need madCodeHook 3.0. When using madCodeHook 2.x, system wide DLL injection doesn't work in 64bit OSs. Most other functionalities of madCodeHook 2.x do work on 64bit OSs, though. •  MSVC++ 2005 Professional (or newer) If you want to hook 64bit processes, too, you need MSVC++, because Delphi does not yet have a native 64bit compiler. If you are only interested in hooking 32bit processes, you can get along with Delphi only. •  code signing certificate (e.g. Verisign), capable of signing drivers The DLL injection drivers shipping with madCodeHook 3.0 do not work without being properly configured and then signed with a code signing certificate. Be cautious when buying a certificate because some support signing of drivers while others don't. With madCodeHook 2.x a code signing certificate was not needed, but then madCodeHook 2.x didn't have a 64bit OS compatible driver.