All of lore.kernel.org
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	libvir-list@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] cirrus: mark as deprecated
Date: Sat, 27 Oct 2018 00:26:33 +0530 (IST)	[thread overview]
Message-ID: <nycvar.YSQ.7.76.1810270008210.7551@xnncv> (raw)
In-Reply-To: <20181026141458.GA493@redhat.com>

+-- On Fri, 26 Oct 2018, Daniel P. Berrangé wrote --+
| ... 
| One thing we should do, however, is to make it clear which of the
| device models we consider secure, and which we consider only usable
| in a friendly guest environment, as we have very different code
| maintainership & quality standards for different parts of QEMU.
| 
| Essentially virtio devices, and then only a handful of the emulated
| devices are things we consider suitable for usage in secure envs.
| Likewise for machine types probably.

True, +1.

It did come up in another thread. It'll surely be helpful to list these 
professional and friendly components. 'Professional' being production ready 
and thus security relevant. And 'Friendly' being experimental or not suitable 
for production usage. Maybe like staging drivers in the kernel tree. They are 
available for use but not considered production ready and thus are not 
security relevant.

To be clear, irrespective of professional or friendly, we strive to fix every 
single issue that is found and/or reported. Only difference is, professional 
ones are tracked by a CVE ID and friendly ones are fixed as bug fixes, not 
tracked by CVE ID.

Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

  reply	other threads:[~2018-10-26 18:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  8:52 [Qemu-devel] [PATCH 0/3] RfC: add support for deprecated devices Gerd Hoffmann
2018-10-25  8:52 ` [Qemu-devel] [PATCH 1/3] qdev: add deprecation_reason to DeviceClass Gerd Hoffmann
2018-10-25 10:50   ` P J P
2018-10-25 11:12   ` Philippe Mathieu-Daudé
2018-10-29  9:19     ` Gerd Hoffmann
2018-10-25  8:52 ` [Qemu-devel] [PATCH 2/3] adlib: mark as insecure and deprecated Gerd Hoffmann
2018-10-25 10:56   ` P J P
2018-10-25 20:40     ` [Qemu-devel] [libvirt] " Daniel P. Berrangé
2018-10-26  7:08       ` P J P
2018-10-26  9:54         ` Daniel P. Berrangé
2018-10-26 12:35           ` P J P
2018-10-25 11:15   ` [Qemu-devel] " Philippe Mathieu-Daudé
2018-10-25 20:27   ` Thomas Huth
2018-10-26  8:48   ` Paolo Bonzini
2018-10-26  9:34     ` P J P
2018-10-26 10:01       ` Paolo Bonzini
2018-10-26 11:53         ` P J P
2018-10-29  9:05           ` Gerd Hoffmann
2018-10-25  8:52 ` [Qemu-devel] [PATCH 3/3] cirrus: mark as deprecated Gerd Hoffmann
2018-10-25 10:59   ` P J P
2018-10-25 11:17   ` Philippe Mathieu-Daudé
2018-10-25 20:28   ` Thomas Huth
2018-10-25 20:37   ` Daniel P. Berrangé
2018-10-26  7:03     ` P J P
2018-10-26  9:42       ` Daniel P. Berrangé
2018-10-26  9:59         ` Daniel P. Berrangé
2018-10-26 10:03           ` Paolo Bonzini
2018-10-26 14:14             ` Daniel P. Berrangé
2018-10-26 18:56               ` P J P [this message]
2018-10-26 10:40         ` Dr. David Alan Gilbert
2018-10-26 13:25         ` [Qemu-devel] [libvirt] " Christian Borntraeger
2018-10-26  8:48     ` Cole Robinson
2018-10-26  9:43       ` Daniel P. Berrangé
2018-10-29  9:12     ` [Qemu-devel] " Gerd Hoffmann
2018-10-30 18:00       ` Daniel P. Berrangé

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=nycvar.YSQ.7.76.1810270008210.7551@xnncv \
    --to=ppandit@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.