I have use madCHook 4.1.2 version.
After I created the driver file (sys), I signed it with SHA 256 + Microsoft Sign (SHA 256), (There is no SHA 1)
In this case, error 577 occurs when calling LoadInjectionDriver in Windows 7-x64.
(For Windows 7-x64/SP1, KB4474419 and KB4490628 for SHA2 sign recognition are updated.
Therefore, no error occurs when installing other Anti-Vaccine product like as BitDefender, etc.)
On WIndows 10-x64, this driver is well loaded.
What should I do?
Thank you for your reply.
But , SHA1 certification is not possible now because the SHA1 certificate is not provided by the vendor (DigiCert, GlobalSign, etc).
https://support.globalsign.com/code-sig ... mestamping
Seems that the only way to make older OSs happy is by using an EV certificate and using the MS Dev Portal. I'd suggest that you ask GlobalSign support how to make that work exactly.
Please understand that this is general code signing issue, and not specific to madCodeHook. If you had your own kernel mode driver, you'd have the same problem. It's not madCodeHook which has such weird code signing requirements, but it's the OS itself. I wish there'd be something I could do to help, but in the end, Microsoft defines the rules...
https://support.ksoftware.net/support/s ... tificates-
"We can provide new SHA-1 certificate for use specifically with legacy systems"
I tried it, but to no avail.
I'm using madCHook 4.1.2.
Currently, the sys file is digital signed with SHA 256 EV Sign and MS Hardware sign,
(There is no SHA1.)
Thank you for your support.
Yes. I think so, I will ask it GlobalSign or Microsoft
and if I get answer, I will let you know.
Thank you again
Without a SHA-1 signature on your binary Windows 7 x64 will never be happy. That's the easiest way that it can be stated unfortunately Microsoft phased out SHA-1 for security reasons and the CA's (Cert Authorities) carried on with SHA-1 until they could not any longer. Some devs grabbed a SHA-1 cert at the last minute and had it renewed for 3 - 5 years, but only if you're one of the lucky ones to do so. It's unfortunate but we are also talking about an OS version that is rather ancient, the grandson of XP and son of Vista so Microsoft started to enforce SHA-2 as of Windows 8.