I'm working on driver signing for Windows as we've modified the default Canon print driver using their tool.
Unfortunately, this removes driver signing and will not work in Server 2012 nor in Windows 8/10.
I need some assistance finding out the exact process for signing an INF (With a supporting Cab file) for installation with Server 2012 and Windows 8/10.
This is the only helpful article I could find: http://pixcl.com/Signing-Windows-8-Drivers.htm
, but I'm worried this won't work in Windows 10. Am I able to use this tutorial using a GoDaddy Driver Signing Certificate? I also read they are phasing out SHA-1 and going SHA-2. Am I able to just replace the SHA-1 with SHA-2 in the tutorial? I want to make sure I don't purchase something I don't need and be out $2,000 (For 5 years and two certs).
The other walkthroughs are too convoluted to find out exactly what needs to be done as it's not a new driver that I'm writing, it's just a modified version of the previously signed driver. That and the driver signing points to all drivers, not print drivers specifically.
Apparently, for Windows 10, they are changing up how drivers work as shown here: http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx
Does this apply to print drivers as well? I need to ensure that the process I'll be pursuing will work in future OS installations.