Blog Post

Hardware Dev Center
1 MIN READ

IMPORTANT: All Partners must reassociate their signing certificates!

kevintremblay's avatar
kevintremblay
Icon for Microsoft rankMicrosoft
Sep 21, 2021
We recently made some changes to Partner Center for Windows Hardware. As a result of these changes, all participants in the hardware program are required to reassociate their valid signing certificat...
Updated Sep 21, 2021
Version 1.0
Igor_Arsenin's avatar
Igor_Arsenin
Copper Contributor
Oct 03, 2021

We also use the COMODO RSA Extended Validation Code Signing Certificate. I have uploaded a new certificate which is reported below in Certificate List. Still I can not submit my drivers for attestation signing. What is the problem? I NEED to SIGN new version of drivers.

 

SignableFile.bin was signed with command line below. All options for sha256 are used. What is wrong? Why type is "CodeSign" instead of "EV CodeSign"?

 

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\signtool.exe" sign /s MY /sha1 "ead1de2a8e66964d3ef1d80ea9c42af953a6fd32" /v /d "FDExt Software" /du "http://www.softlab-nsk.com" /tr http://timestamp.comodoca.com/rfc3161 /td sha256 /fd sha256 SignableFile.bin 


"OOO ""SoftLab-NSK"""EAD1DE2A8E66964D3EF1D80EA9C42AF953A6FD32CodeSign01.12.202210.03.2021 07:40:35ZCN=COMODO RSA Extended Validation Code Signing CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBАктивные
https://partner.microsoft.com/ru-ru/dashboard/account/managecertificates#