[wdmaudiodev] Re: How to sign up with MS with the Win10 driver no charge "attestment" option

  • From: "Paul Titchener" <pt@xxxxxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Mon, 26 Oct 2015 11:40:32 -0700

Tim, to be candid I know just enough about these certs to be dangerous, but
here’s my understanding of this cert.

Its an EV cert we got recently from DigiCert, one of MS’s recommended 2
suppliers for driver certs on the MS drivers dev site.

We used it to both sign up with MS’s driver’s approval site and also to submit
our driver package which they accepted so it passed their tests.

The reason I’m calling it an SHA1 cert is when you use the File Explorer and do
a Properties->Digital Signatures on it, under the heading “Digest Algorithm” it
lists SHA1.

But if you then click Details->Advanced, in the page that comes up its lists
SHA1 again for Digest Algorithm but in the field labeled Issurer it states:

DigiCert EV Code Signing CA (SHA2) ...

So perhaps this Issuer field that does contain a SHA2 description is the one I
should be referring to when describing this cert, is that correct?


Paul Titchener

From: Tim Roberts
Sent: Monday, October 26, 2015 11:21 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: How to sign up with MS with the Win10 driver no
charge "attestment" option

Paul Titchener wrote:

We’re detecting the OS during installation and only installing the MS SHA256
cert drivers on Win 10, earlier machines get drivers with just our SHA1 EV cert.

I do not believe there is any such thing as an SHA1 EV cert. Are you sure it's
not SHA2? Where did you get it?

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

Other related posts: