W
Wade_Dawson
Guest
Hi All. We have a driver that builds correctly using vs2019 Pro, 16.4.4 with wdk 10.0.18346.1000. However, when the solution containing the same .vcxproj is built under ewdk 19h1_release_svc_prod3.18362.84, test-signing is being performed even though the .vcxproj has driver signing set to off for all architecture and targets. Additionally no other driver-ish tasks are being performed by this build; no package project, no inf2cat, etc. Just a (seemingly) simple compile. I have looked through the .vcxproj file and can't see any mention of a test-signing being requested.
Any thoughts are greatly appreciated!
I thought I would add that there are 2 reasons I even care: 1) The WdkTest cert signature is getting propagated all the way through to the final attestation-signed binary, possibly confusing a user or anti-malware software, and 2) the driver is failing to load with a signature violation even though the required sigs are there. I'm suspecting having the nasty SHA1 test-sig first may be causing a problem.
PS> Being completely at a loss as to why this is happening, I've added a "signtgool remove /s xxx.sys" right before production signing the driver binaries, which is doing the trick.
Continue reading...
Any thoughts are greatly appreciated!
I thought I would add that there are 2 reasons I even care: 1) The WdkTest cert signature is getting propagated all the way through to the final attestation-signed binary, possibly confusing a user or anti-malware software, and 2) the driver is failing to load with a signature violation even though the required sigs are there. I'm suspecting having the nasty SHA1 test-sig first may be causing a problem.
PS> Being completely at a loss as to why this is happening, I've added a "signtgool remove /s xxx.sys" right before production signing the driver binaries, which is doing the trick.
Continue reading...