xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Moritz Mühlenhoff" <muehlenhoff@univention.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: Avoiding the use of test signing for the GPLPV drivers for 64 bit Windows
Date: Mon, 22 Aug 2011 09:40:54 -0400	[thread overview]
Message-ID: <20110822134054.GE8944@dumpdata.com> (raw)
In-Reply-To: <201108221202.22148.muehlenhoff@univention.de>

On Mon, Aug 22, 2011 at 12:02:21PM +0200, Moritz Mühlenhoff wrote:
> Hi,
> we've been investigating ways to deploy the GPLPV drivers for Windows 2008
> w/o the need to activate the test mode (not for strictly technical reasons; 
> the drivers work fine but some third party applications void their warranty 
> if run under test mode and the mandatory note on the desktop may lead to user
> confusion).
> 
> I found a mailing lis thread, where a similar scenario has been discussed
> for the libusb drivers. The relevant bits start here:
> http://libusb.6.n5.nabble.com/WHQL-Testing-Agreement-and-GPLv3-conflicts-td3335877.html
> 
> Microsoft doesn't permit GPLv2 und GPLv3 drivers in their Windows Logo
> Program (which is a prerequisite for WHQL certification). However in this
> thread someone from Wind River contacted Microsoft and they pointed to the
> possibility to sign the driver with a certificate issues by a CA instead of
> the WHQL signatures (the full document is attached to the second link):
> 
> http://libusb.6.n5.nabble.com/WHQL-Testing-Agreement-and-GPLv3-conflicts-tp335877p3337666.html
> http://libusb.6.n5.nabble.com/WHQL-Testing-Agreement-and-GPLv3-conflicts-tp3335877p3341534.html
> 
> In my understanding this certificate would be a SPC certificate
> http://msdn.microsoft.com/en-us/library/ff552299%28v=vs.85%29.aspx
> http://www.certum.eu/certum/cert,offer_software_publisher.xml
> 
> Later on in the thread it's being confirmed that this procedure allows the
> installation of the driver w/o popups and activation of the test mode:
> http://libusb.6.n5.nabble.com/WHQL-Testing-Agreement-and-GPLv3-conflicts-tp3335877p3339827.html
> 
> Is anyone already building and signing  the GPLPV drivers with that procedure?

Hm sounds like that is exactly what the Red Hat folks had done:

http://git.kernel.org/?p=virt/kvm/kvm-guest-drivers-windows.git;a=blob;f=VirtIO/LICENSE;h=808dba85afaccc31dac21863d2cd4dd4a3b7d29f;hb=HEAD
> 
> Cheers,
> Moritz
> -- 
> Moritz Mühlenhoff                         muehlenhoff@univention.de
> Open Source Software Engineer and Consultant
> Univention GmbH  Linux for Your Business     fon: +49 421 22 232- 0
> Mary-Somerville-Str.1  28359 Bremen          fax: +49 421 22 232-99
> http://www.univention.de
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2011-08-22 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 10:02 Avoiding the use of test signing for the GPLPV drivers for 64 bit Windows Moritz Mühlenhoff
2011-08-22 13:40 ` Konrad Rzeszutek Wilk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110822134054.GE8944@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=muehlenhoff@univention.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).