First published on MSDN on Nov 13, 2017
On March 9th, Hardware Dev Center will no longer accept HLKx, HCKx, Attestation .CAB, and WLK packages signed using a SHA-1 digest algorithm and certificate chain. This change may require that your Hardware Dev Center associated certificates (EV and others) be updated. This is being done to support our SHA-1 Enforcement plan outlined on TechNet and to increase our confidence that the package contents have not been altered. Packages already submitted prior to this change will not be affected or re-signed.
When will this change go into effect?
March 9th 2018
Do I need to change how I code sign driver binaries (.exe, .sys, .dll)?
No . This change does NOT affect how you code sign your driver files (.exe, .sys, .dll). We are only enforcing that your HLKx, HCKx, CAB, WLK packages are signed with a SHA-2 digest algorithm and certificate chain.
What do I need to do differently?
How do I check if my Hardware Dev Center certificates are signed with SHA-2?
Certificates cannot be downloaded from Hardware Dev Center so you will need to use your local certificate.
How do I update the certificate associated with my DevCenter account?
Windows 7/Server 2008 R2 and lower | Windows 8/8.1 | Windows 10 |
SHA-1 only | SHA-2 only | SHA-2 only |
How will DevCenter sign my binaries?
Windows 7/Server 2008 R2 and lower | Windows 8/8.1 | Windows 10 |
SHA-2 only | SHA-2 only | SHA-2 only |
How do I enable SHA-2 support for Windows 7 / Server 2008 R2 RTM?
To enable SHA-2 support on Windows 7 / Server 2008 R2 please refer to Microsoft Security Advisory 3033929.
For questions not answered here, please contact your Microsoft representative. We will update this FAQ occasionally with more info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.