Hmmm,
then build a driver without adding a certificate... ?? How about this?
Hp
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Vincent Burel (VB-Audio)
Sent: Donnerstag, 8. Oktober 2015 17:21
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?
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).
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
De la part de Tom Eckert
Envoyé : jeudi 8 octobre 2015 16:20
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?
It's still working for us. But, while we're on the subject, can someone
clarify this:
What about existing drivers? Do I need to re-sign these drivers to get them to
work with Windows 10?
No, existing drivers do not need to be re-signed. To ensure backwards
compatibility, drivers which are properly signed by a
<https://msdn.microsoft.com/en-us/library/windows/hardware/ff548231%28v=vs.85%29.aspx>
valid cross-signing certificate that was issued before the release of Windows
10 will continue to pass signing checks on Windows 10.
Does this mean that drivers which are properly signed by a valid cross-signing
certificate that was issued before the release of Windows 10 but which are
built and signed after the release date, grace period, whatever will work or
not? So, not existing drivers, but new drivers signed with a certificate that
satisfies the above condition.
Thanks,
Tom
On 10/8/2015 9:34 AM, Vincent Burel (VB-Audio) wrote:
No, it does not work anymore on WIN10 release, this is what I’ve experimented
last days when building a new driver version,
This is also explained there:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
De la part de Tom Eckert
Envoyé : jeudi 8 octobre 2015 15:22
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?
If you have a code signing certificate that was issued before the Win10 release
date, you can continue to use it with the old driver signing method until it
expires.
Tom Eckert
On 10/8/2015 3:02 AM, Vincent Burel (VB-Audio) wrote:
Hello,
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? )
Consequently we need to register on Microsoft DashBoard
(https://sysdev.microsoft.com/) and sign different agreements…
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 ?
What is the technical and financial risk ? (some agreement are about technical
constraint , some other talk about paying Microsoft for testing services).
Regards
Vincent Burel
