Right. According to the announcements at WinHEC, as described in my blog post at: http:</http:>
“Drivers signed before Windows 10 RTM will be able to use the older signing mechanisms. But once Windows 10 ships, if you want your driver to run on Windows 10 desktop systems, you?ll need to (a) get an EV certificate, (b) using that signature submit your driver to sysdev to get Microsoft?s signature.”
That’s why we thought it was pretty important for people to start dealing with this back in March, months before Win10 RTM. Get your stuff updated, signed the old way before Win10 RTM, and you SHOULD be GTG for Win10 according to this announcement.
ALTERNATIVELY, get an EV Cert, work through the new procedures, and get your stuff signed at your leisure and you’re GTG. That’s what WE chose to do.
That’s all *I* know. I haven’t heard anything to the contrary in the intervening months, but then again, I haven’t done anything to specifically follow-up on this either.
Of course, this *does* beg the question as to how you ever update your drivers after Win10 RTM if you don’t get an EV Cert and have them signed by MSFT’s program. According to what’s been announced so far, the answer to that is “you don’t… After Win10 RTM you have to get an EV Cert and get your drivers signed by MSFT’s program.” Well see if that sticks. Like I said, I haven’t done anything to follow-up on this personally.
There is absolutely nothing in the guidelines that says you have to incorporate.
This isn’t that mysterious… just Google “Guidelines For The Issuance And Management Of Extended Validation Certificates” and read what the requirements are for an EV cert.
NOW… what a given Certification Authority may be willing to do CAN be more limited than these guidelines allow. But non-incorporated business entities are certainly allowable (consider all the general partnerships that would be ruled-out if this were not possible).
Peter
OSR
@OSRDrivers