qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>, P J P <ppandit@redhat.com>
Subject: Re: About 'qemu-security' mailing list
Date: Mon, 14 Sep 2020 09:54:58 +0100	[thread overview]
Message-ID: <20200914085458.GA1252186@redhat.com> (raw)
In-Reply-To: <CAFEAcA_9BVbqFCHJqS8jj6L3OqVNc60NCjAjRs516VyLH2EFfw@mail.gmail.com>

On Fri, Sep 11, 2020 at 04:51:49PM +0100, Peter Maydell wrote:
> On Fri, 11 Sep 2020 at 15:22, P J P <ppandit@redhat.com> wrote:
> > Proposal: (to address above limitations)
> > =========
> >
> > * We set up a new 'qemu-security' mailing list.
> >
> > * QEMU security issues are reported to this new list only.
> >
> > * Representatives from various communities subscribe to this list. (List maybe
> >    moderated in the beginning.)
> >
> > * As QEMU issues come in, participants on the 'qemu-security' list shall
> >    discuss and decide about how to triage them further.
> 
> Way way back, the idea of a qemu-security list was proposed, and
> it was decided against because there wasn't a clear way that
> people could send encrypted mail to the security team if it
> was just a mailing list. So that's why we have the "handful
> of individual contacts" approach. Is that still something people
> care about ?
> 
> My question is, who decides who's on the qemu-security list?
> Is this just "it's the same handful of contacts, but they
> have a mailing list for convenience" ? It sounds like you
> want it to be a larger grouping than that and maybe also
> want to use it as a mechanism for informing downstream distros
> etc about QEMU security issues, which is to say you're
> proposing an overhaul and change to our security process,
> not merely "we'd like to create a mailing list" ?

Yes, that is a reasonable description. 

Do we think the current QEMU security process is working well for the
community as a whole in terms of our downstream consumers learning about
security flaws in an appropriate timeframe and manner ?  

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2020-09-14  9:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 14:20 About 'qemu-security' mailing list P J P
2020-09-11 15:27 ` Li Qiang
2020-09-11 15:40 ` Alexander Bulekov
2020-09-11 15:58   ` Alexander Bulekov
2020-09-18  7:33   ` P J P
2020-09-11 15:47 ` Daniel P. Berrangé
2020-09-11 15:51 ` Peter Maydell
2020-09-14  7:38   ` Philippe Mathieu-Daudé
2020-09-14 10:17     ` Stefan Hajnoczi
2020-09-14  8:54   ` Daniel P. Berrangé [this message]
2020-09-14  9:30     ` Peter Maydell
2020-09-14 10:15   ` Stefan Hajnoczi
2020-09-15 10:48     ` P J P
2020-09-16 11:10       ` Stefan Hajnoczi
2020-09-16 12:33         ` Peter Maydell
2020-09-16 13:06           ` Daniel P. Berrangé
2020-09-16 13:25             ` Thomas Huth
2020-09-16 13:30               ` Daniel P. Berrangé
2020-09-18  7:02         ` P J P
2020-09-30 11:46           ` P J P
2020-09-30 15:48           ` Darren Kenny
2020-10-01 10:35             ` P J P
2020-10-01 11:34               ` Darren Kenny
2020-10-01 13:57                 ` Konrad Rzeszutek Wilk
2020-10-01 18:17                 ` P J P
2020-10-16 14:17                   ` P J P
2020-10-20 14:08                     ` P J P
2020-11-03 11:18                       ` P J P
2020-11-17 14:46                     ` Stefan Hajnoczi
2020-11-17 16:19                       ` Stefan Hajnoczi
2020-11-17 16:35                         ` Daniel P. Berrangé
2020-11-18 10:32                           ` P J P

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=20200914085458.GA1252186@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=ppandit@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 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).