2016-09-14 16:53 signed windows 10 drivers:
The best resource for this process is clearly David Graysons Practical Windows Code and Driver Signing
Here are the refined points in that article for aparticular use case: Windows 7 and greater. Installing a driver package without loading a kernel module.
Go to GlobalSign. Use their challenging interface to sign up for the "Code Signing" product. This costs about $219. Do this first as they then have to "verify your identity". For Wasatch Photonics, this meant calling us on the phone and telling us that we needed to provide more documentation that we were a real company. This is after I pointed them to the our NC official records showing our phone number. I had to suggest we would move to a competitor certificate service provider before things started to progress. After this is complete, download the .pfx file into the same directory as the drivers to sign. This is the most difficult and time consuming part of the process.
Download and install the Windows Driver Kit
Use your INF files of choice. We modified the provided Cypress FX2/FX3 Drivers.
Modify the INF files to include your custom Vendor ID and Product ID:
Convert the modified INF file into a CAT file:
"C:\Program Files (x86)\Windows Kits\10\bin\x86\inf2cat"
From David's instructions: "Be sure to install GlobalSign's R1-R3 cross-certificate on the computer that will be making signatures." This means download the r1cross.cer right click it and select "install certificate", then accept all the defaults.
Then run the command to actually sign the drivers:
"C:\Program Files (x86)\Windows Kits\10\bin\x86\signtool"
/n "Wasatch Photonics"
Then copy the signed files (minus the PFX key and instructions) to the INF_DRIVERS folder distributed as part of the installer build. And example below is included for InnoSetup
Filename: "pnputil"; Parameters: "-i -a
StatusMsg: "Installing WP drivers (this may take a few seconds) ...";