qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Lee Lambert <davidl@lmert.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1130095] Re: Windows Signed Drivers
Date: Sat, 01 Feb 2014 00:36:08 -0000	[thread overview]
Message-ID: <20140201003608.1668.7801.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 20130219122841.31745.15815.malonedeb@soybean.canonical.com

** Description changed:

- Hello!
+ ReactOS has a general offer (subject to certain conditions, which may or
+ may not be reasonable for the qemu virtual-IO drivers) to sign Open
+ Source components with their certificate.
+ 
  http://www.reactos.org/wiki/Driver_Signing
- If it helps you :)
- Free signing you windows drivers.
+ 
+ The files in "virtio-win-0.1-74.iso" appear not to be signed, hence
+ trigger a warning on Windows 2008 R2.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1130095

Title:
  Windows Signed Drivers

Status in QEMU:
  New

Bug description:
  ReactOS has a general offer (subject to certain conditions, which may
  or may not be reasonable for the qemu virtual-IO drivers) to sign Open
  Source components with their certificate.

  http://www.reactos.org/wiki/Driver_Signing

  The files in "virtio-win-0.1-74.iso" appear not to be signed, hence
  trigger a warning on Windows 2008 R2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1130095/+subscriptions

       reply	other threads:[~2014-02-01  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130219122841.31745.15815.malonedeb@soybean.canonical.com>
2014-02-01  0:36 ` David Lee Lambert [this message]
2014-02-02 13:17 ` [Qemu-devel] [Bug 1130095] Re: Windows Signed Drivers Yan Vugenfirer

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=20140201003608.1668.7801.launchpad@soybean.canonical.com \
    --to=davidl@lmert.com \
    --cc=1130095@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /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).