[wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?

  • From: Tim Roberts <timr@xxxxxxxxx>
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Thu, 8 Oct 2015 11:18:52 -0700

Vincent Burel (VB-Audio) wrote:

As far as I see; WIN10 does not allow Installation of driver signed
after its Release Date.

In other words, doing a driver package today for WIN10 is not possible
anymore without using the Microsoft Signing Services.

(please confirm or if there is a workaround? )

That's not exactly true, but the situation is complicated. If you have
an SHA1 or SHA2 certificate that was issued prior to the RTM date, you
can continue to use it to sign driver packages "the old way," and Win 10
will load them. Once your existing certificate expires, or if you
didn't get a certificate before that date, then you have to use the
attestation process through the WHQL dashboard, which requires an EV
SHA2 certificate.

*So I have basically 2 questions:*

What is the exact list of Agreements that must be signed to be able to
make code-signing on an audio driver ?

It is a long list (two dozen?) of agreements and addenda, everything
from the use of the logo, to known exceptions, to quality promises, to
ethical considerations. Nothing too onerous. Everyone who has ever
submitted to WHQL has gone through it.

What is the technical and financial risk ? (some agreement are about
technical constraint , some other talk about paying Microsoft for
testing services).

Payment is only an issue if you intend to go through WHQL testing or get
the Windows logo. Attestation does not require payment.

Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.

Other related posts: