CODEWITHSUNDEEP
cwindowsdriver
hsluoyz
hsluoyz

Reputation: 2919

Can I use a non-EV certificate to sign a driver after Windows 10 RTM release?

I am developing a kernel-mode driver and I 'd like it to be able to run on all Windows platforms (including Windows 10). I have read the driver signing policy in Win10 from http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx. I don't know if I am understanding it right, does it mean that if I buy a non-EV cert before Win10 release (AKA 2015/7/29), I can still use the cert to sign a driver to any platform including Win10 until the cert expires. For example, I can just buy a 3-year long cert before 7/29 and use it to sign any drivers for these 3 years (the longest period for a cert seems to be 3 years). 3 years later, I have no other choice but to buy an EV cert, is this understanding right? Thanks.

Upvotes: 1

Views: 966

Answers (1)

paulsm4
paulsm4

Reputation: 121799

You're basically asking if you can slip a driver that wasn't signed with Extended Validation ("EV") certificate through the door before Windows 10 release.

The salient point is this:

http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx

Beginning with the release of Windows 10, all new Windows 10 kernel mode drivers must be submitted to and digitally signed by the Windows Hardware Developer Center Dashboard portal. Windows 10 will not load new kernel mode drivers which are not signed by the portal.

My guess is "maybe".

But you'd better hurry.

And you'd better have a Plan B if your Windows 10 customers discover that your driver won't work.

Upvotes: 1

Related Questions