Message 3 of 4
08 Feb 18 11:45
Join Date: 20 Dec 2010
Posts To This List: 27
Windows 10 Code signing
> We'll need to sign driver with an EV code signing cert
> and submit it to their dashboard.
As Tim said, this is correct, although there is a further
clarification to make there. You will need to HAVE an EV certificate,
and you will need to have registered that EV certificate with a
company account you created on the Microsoft Windows Dev Center
So long as you register your existing Class 3 certificate on the
portal company account too, you can continue performing your actual
/driver signing/, including the submissions of any .CABs, .HLKX and/or
.HCKX files, using the Class 3 certificate you're using today.
You simply must _have_ an EV certificate registered to "prove"
identity of whom owns the company account you created on the Microsoft
Windows Dev Center portal. But once that trust is established, they
will trust any additional non-EV certificates you upload to your
company account, too.
So an EV certificate is required, but not specifically "to sign every
driver", nor even to "sign every submission upload." Its fine if you
/do/ use the EV certificate to perform your actual driver signing
and/or submissions, but that's not strictly required, if you have
other non-EV certificates registered too.
There do happen to be Windows Dev Center submissions that _require_
being signed with the EV certificate, but those are things like UEFI
firmware submissions, and not general driver signing.
Client for Open Enterprise Server