[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[win-pv-devel] On the state of non-test-signed WinPV drivers

  • To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Stephen Oberholtzer <stevie@xxxxxxxxx>
  • Date: Fri, 1 Jul 2016 19:36:34 -0400
  • Delivery-date: Fri, 01 Jul 2016 23:36:43 +0000
  • List-id: Developer list for the Windows PV Drivers subproject <win-pv-devel.lists.xenproject.org>


I have some questions about the whole signed-drivers thing, so I hope you'll indulge me.

(1) As best as I can tell, only test-signed drivers are currently being posted. Is that correct?

(2) Test-signed is pretty clear to me, but what is the difference between release-signed and logo-signed?

(3) If I want PV drivers that can be installed on a standard Windows installation without any hassle, do they need to be release-signed or logo-signed?

(4)  What do you guys need in order to be able to distribute #3?   What can I do to help?

I searched around, and it looks like the following are needed:

* Windows Hardware Developer Center Dashboard portal account (no idea how much this costs)
* An appropriate EV certificate
** GlobalSign - $410/yr, $760 for 2 years, or $950 for 3 years
** DigiCert - $449/yr, $798 for 2 years, or $993 for 3 years
** Entrust - $399/yr, no multiyear discount (so best value for 1 year but that's it)
* To get an EV certificate, you need a legally-recognized entity (which can be a full-blown corporation or an LLC)
* Then you need to run some tests and submit them to Microsoft and their system signs the drivers on your behalf.

-- Stevie-O
Real programmers use COPY CON PROGRAM.EXE

win-pv-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.