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

  • From: "Vincent Burel \(VB-Audio\)" <vincent.burel@xxxxxxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Fri, 9 Oct 2015 08:16:00 +0200

Ha, just saw my exported CER was outdated, and the signing procedure does not
produce error in this case… already got the problem some years ago.

Sorry, but happy to be wrong.

Vincent Burel



De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
De la part de Vincent Burel (VB-Audio)
Envoyé : vendredi 9 octobre 2015 07:39
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?



this is what I’ve experienced this week.



I’ve signed one of my audio driver with my usual certificate (issued last
year), and installed it on WIN10 (fresh installed)

The driver was marked disabled with a error regarding certificate.



Will do more complete test this month.

Regards

Vincent Burel



De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
De la part de Tim Roberts
Envoyé : jeudi 8 octobre 2015 20:26
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?



Vincent Burel (VB-Audio) wrote:

Yes, Drivers signed before the WIN10 release date still work…

The problem is when you sign the driver today (whatever the expiration date of
your certificate).


You have repeated this, but it is simply not true. If your certificate was
issued prior to the Win 10 RTM date (August 1), you can continue to use it for
signing new drivers using the same method you've always used. You don't have
to change anything until your certificate expires. Then you're locked in to
the attestation process.

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

Other related posts: