Home
%3CLINGO-SUB%20id%3D%22lingo-sub-364916%22%20slang%3D%22en-US%22%3EStarting%20in%20March%202018%2C%20packages%20signed%20using%20a%20SHA-1%20digest%20algorithm%20and%20certificate%20chain%20will%20no%20longer%20be%20accepted%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364916%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFirst%20published%20on%20MSDN%20on%20Nov%2013%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3EOn%20March%209th%2C%20Hardware%20Dev%20Center%20will%20no%20longer%20accept%20HLKx%2C%20HCKx%2C%20Attestation%20.CAB%2C%20and%20WLK%20packages%20signed%20using%20a%20SHA-1%20digest%20algorithm%20and%20certificate%20chain.%20This%20change%20may%20require%20that%20your%20Hardware%20Dev%20Center%20associated%20certificates%20(EV%20and%20others)%20be%20updated.%20This%20is%20being%20done%20to%20support%20our%20%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2Fwiki%2Fcontents%2Farticles%2F32288.windows-enforcement-of-sha1-certificates.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20SHA-1%20Enforcement%20plan%20outlined%20on%20TechNet%20%3C%2FA%3E%20and%20to%20increase%20our%20confidence%20that%20the%20%3CSTRONG%3E%20package%20contents%20%3C%2FSTRONG%3E%20have%20not%20been%20altered.%20Packages%20already%20submitted%20prior%20to%20this%20change%20will%20not%20be%20affected%20or%20re-signed.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1678879277%22%20id%3D%22toc-hId-1705808386%22%3EFAQ%3C%2FH2%3E%0A%3CP%3E%3CBR%20%2F%3E%20%3CSTRONG%3EWhen%20will%20this%20change%20go%20into%20effect%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3EMarch%209th%202018%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3E%20Do%20I%20need%20to%20change%20how%20I%20code%20sign%20driver%20binaries%20(.exe%2C%20.sys%2C%20.dll)%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CSTRONG%3E%20No%20%3C%2FSTRONG%3E%20.%20This%20change%20does%20NOT%20affect%20how%20you%20code%20sign%20your%20driver%20files%20(.exe%2C%20.sys%2C%20.dll).%20We%20are%20only%20enforcing%20that%20your%20HLKx%2C%20HCKx%2C%20CAB%2C%20WLK%20packages%20are%20signed%20with%20a%20SHA-2%20digest%20algorithm%20and%20certificate%20chain.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3E%20What%20do%20I%20need%20to%20do%20differently%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EWhen%20signing%20your%20HLKx%2C%20HCKx%2C%20WLK%2C%20or%20CAB%20package%20for%20submission%2C%20use%20SHA-2%20as%20the%20default%20signature%20digest%20algorithm%20and%20a%20SHA-2%20timestamp.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EVerify%20the%20certificates%20associated%20with%20your%20Hardware%20Dev%20Center%20profile%20are%20SHA-2%20and%20re-sign%20them%20using%20the%20%3CSTRONG%3E%20%2Ffd%20sha256%20%3C%2FSTRONG%3E%20switch%20and%20appropriate%20SHA-2%20timestamp%2C%20if%20needed.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EFor%20HLKx%2C%20HCKx%2C%20Attestation%20.CAB%20and%20WLK%20packages%2C%20add%20the%20%3CSTRONG%3E%20%2Ffd%20sha256%20%3C%2FSTRONG%3E%20switch%20and%20a%20%3CSTRONG%3E%20ppropriate%20SHA-2%20timestamp%20%3C%2FSTRONG%3E%20to%20your%20signtool%20process.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CBR%20%2F%3E%20%3CSTRONG%3EHow%20do%20I%20check%20if%20my%20Hardware%20Dev%20Center%20certificates%20are%20signed%20with%20SHA-2%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3ECertificates%20cannot%20be%20downloaded%20from%20Hardware%20Dev%20Center%20so%20you%20will%20need%20to%20use%20your%20local%20certificate.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EOpen%20your%20local%20.CER%20file%20by%20double-clicking%20it%20or%20run%20%E2%80%9Ccertmgr.msc%E2%80%9D%20to%20locate%20and%20open%20it.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EClick%20the%20%3CSTRONG%3E%20Details%20%3C%2FSTRONG%3E%20tab%20and%20verify%20the%20Signature%20algorithm%20and%20Signature%20hash%20algorithm%20are%20SHA256RSA%20and%20SHA256%20respectively.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20845px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F86569i84BC1D38EBA560E6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3E%20How%20do%20I%20update%20the%20certificate%20associated%20with%20my%20DevCenter%20account%3F%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CDIV%3E%3CEM%3E*Note%3A%20Only%20your%20portal%20Administrators%20have%20permissions%20to%20modify%20and%20upload%20these%20certificates.%20%3C%2FEM%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CUL%3E%0A%3CUL%3E%0A%3CLI%3ESign%20in%20as%20the%20Company%20Administrator.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EClick%20the%20gear%20icon%20%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%2025px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F86570iF1E787683CDF6F57%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20in%20the%20upper%20right%2C%20then%20click%20%3CSTRONG%3E%20Account%20settings%20%3C%2FSTRONG%3E%20%2C%20then%20%3CSTRONG%3E%20Manage%20Certificates%20%3C%2FSTRONG%3E%20on%20the%20left%20pane.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EClick%20the%20%3CSTRONG%3E%20Add%20a%20new%20certificate%20%3C%2FSTRONG%3E%20button%20and%20follow%20the%20upload%20process.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EDownload%20%3CSTRONG%3E%20Signablefile.bin%20%3C%2FSTRONG%3E%20from%20the%20Hardware%20Dev%20Center%20dashboard%2C%20and%20sign%20it%20with%20the%20new%20digital%20certificate%20for%20your%20company%20using%20%3CSTRONG%3E%20SignTool%20%3C%2FSTRONG%3E%20with%20the%20following%20switch%20%E2%80%9C%20%3CSTRONG%3E%20%2Ffd%20sha256%20%3C%2FSTRONG%3E%20%E2%80%9D%20and%20appropriate%20SHA-2%20timestamp.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EUpload%20the%20signed%20file%20to%20the%20Hardware%20Dev%20Center%20dashboard.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%3CBR%20%2F%3E%20%3CSTRONG%3EWhere%20do%20I%20get%20a%20SHA-2%20certificate%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3ESee%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fget-a-code-signing-certificate%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Get%20a%20code%20signing%20certificate%20%3C%2FA%3E%20for%20more%20information.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EDo%20I%20need%20to%20change%20how%20I%20code%20sign%20driver%20binaries%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3ENo.%20At%20this%20stage%20we%20are%20not%20blocking%20SHA-1%20code%20signed%20binaries.%20We%20are%20only%20blocking%20HLKx%2C%20HCKx%2C%20CAB%2C%20WLK%20packages%20signed%20with%20a%20SHA-1%20digest%20algorithm%20and%20certificate%20chain.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EHow%20will%20DevCenter%20sign%20my%20catalog%20(.CAT)%20file%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FDIV%3E%0A%3CTABLE%20style%3D%22height%3A%2087px%3B%22%3E%0A%3CTBODY%3E%0A%3CTR%20style%3D%22height%3A%2029px%3B%22%3E%0A%3CTD%20style%3D%22width%3A%2096px%3B%20height%3A%2029px%3B%22%3E%3CSTRONG%3EWindows%207%2FServer%202008%20R2%20and%20lower%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2090px%3B%20height%3A%2029px%3B%22%3EWindows%208%2F8.1%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2090px%3B%20height%3A%2029px%3B%22%3EWindows%2010%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%20style%3D%22height%3A%2029px%3B%22%3E%0A%3CTD%20style%3D%22width%3A%2096px%3B%20height%3A%2029px%3B%22%3E%3CSTRONG%3E%20SHA-1%20only%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2090px%3B%20height%3A%2029px%3B%22%3ESHA-2%20only%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2090px%3B%20height%3A%2029px%3B%22%3ESHA-2%20only%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EHow%20will%20DevCenter%20sign%20my%20binaries%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%20style%3D%22height%3A%20138px%3B%22%3E%0A%3CTD%20style%3D%22width%3A%2082.6667px%3B%20height%3A%20138px%3B%22%3E%3CSTRONG%3EWindows%207%2FServer%202008%20R2%20and%20lower%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2078px%3B%20height%3A%20138px%3B%22%3EWindows%208%2F8.1%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2078.6667px%3B%20height%3A%20138px%3B%22%3EWindows%2010%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%20style%3D%22height%3A%2056px%3B%22%3E%0A%3CTD%20style%3D%22width%3A%2082.6667px%3B%20height%3A%2056px%3B%22%3E%3CSTRONG%3E%20SHA-2%20only%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2078px%3B%20height%3A%2056px%3B%22%3ESHA-2%20only%3C%2FTD%3E%0A%3CTD%20style%3D%22width%3A%2078.6667px%3B%20height%3A%2056px%3B%22%3ESHA-2%20only%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%3CBR%20%2F%3E%20%3CSTRONG%3EHow%20do%20I%20enable%20SHA-2%20support%20for%20Windows%207%20%2F%20Server%202008%20R2%20RTM%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3ETo%20enable%20SHA-2%20support%20on%20Windows%207%20%2F%20Server%202008%20R2%20please%20refer%20to%20Microsoft%20Security%20Advisory%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fsecurity%2F3033929%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%203033929.%20%3C%2FA%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20questions%20not%20answered%20here%2C%20please%20contact%20your%20Microsoft%20representative.%20We%20will%20update%20this%20FAQ%20occasionally%20with%20more%20info.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-364916%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20MSDN%20on%20Nov%2013%2C%202017%20On%20March%209th%2C%20Hardware%20Dev%20Center%20will%20no%20longer%20accept%20HLKx%2C%20HCKx%2C%20Attestation%20.%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Not applicable

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.

FAQ


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?

    • When signing your HLKx, HCKx, WLK, or CAB package for submission, use SHA-2 as the default signature digest algorithm and a SHA-2 timestamp.

 

    • Verify the certificates associated with your Hardware Dev Center profile are SHA-2 and re-sign them using the /fd sha256 switch and appropriate SHA-2 timestamp, if needed.

 

    • For HLKx, HCKx, Attestation .CAB and WLK packages, add the /fd sha256 switch and a ppropriate SHA-2 timestamp to your signtool process.


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.

    • Open your local .CER file by double-clicking it or run “certmgr.msc” to locate and open it.

 

    • Click the Details tab and verify the Signature algorithm and Signature hash algorithm are SHA256RSA and SHA256 respectively.


How do I update the certificate associated with my DevCenter account?

*Note: Only your portal Administrators have permissions to modify and upload these certificates.

    • Sign in as the Company Administrator.
    • Click the gear icon in the upper right, then click Account settings , then Manage Certificates on the left pane.
    • Click the Add a new certificate button and follow the upload process.
    • Download Signablefile.bin from the Hardware Dev Center dashboard, and sign it with the new digital certificate for your company using SignTool with the following switch “ /fd sha256 ” and appropriate SHA-2 timestamp.
    • Upload the signed file to the Hardware Dev Center dashboard.

Where do I get a SHA-2 certificate?
See Get a code signing certificate for more information.

Do I need to change how I code sign driver binaries?
No. At this stage we are not blocking SHA-1 code signed binaries. We are only blocking HLKx, HCKx, CAB, WLK packages signed with a SHA-1 digest algorithm and certificate chain.

How will DevCenter sign my catalog (.CAT) file?

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.