madConfigDrv creates wrong checksum
Posted: Thu Feb 11, 2016 6:52 am
ex)
madConfigDrv DemoDriver32.sys HookProcessCreationDemoDriver HookProcessCreation32.dll -unsafeStopAllowed
madConfigDrv DemoDriver64.sys HookProcessCreationDemoDriver HookProcessCreation32.dll HookProcessCreation64.dll -unsafeStopAllowed
When created a Hooking Driver with reference to the above example,
The CheckSum value of IMAGE_OPTIONAL_HEADER in PE structure of sys file contained an invalid value.
If digitally signed the hooking driver by signtool.exe in Windows 10, driver wasn't loaded due to a checksum problem.
(In Windows 8.1 and earlier versions, it puts correct CheckSums after digitally signing.)
I am currently using madCodeHook 3.1.10.
Is it possible to check the problem and patch for the problem above?
madConfigDrv DemoDriver32.sys HookProcessCreationDemoDriver HookProcessCreation32.dll -unsafeStopAllowed
madConfigDrv DemoDriver64.sys HookProcessCreationDemoDriver HookProcessCreation32.dll HookProcessCreation64.dll -unsafeStopAllowed
When created a Hooking Driver with reference to the above example,
The CheckSum value of IMAGE_OPTIONAL_HEADER in PE structure of sys file contained an invalid value.
If digitally signed the hooking driver by signtool.exe in Windows 10, driver wasn't loaded due to a checksum problem.
(In Windows 8.1 and earlier versions, it puts correct CheckSums after digitally signing.)
I am currently using madCodeHook 3.1.10.
Is it possible to check the problem and patch for the problem above?