All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: sstabellini@kernel.org, pmatouse@redhat.com,
	qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	pjp@redhat.com
Subject: Re: [qemu-web PATCH v2] Add "Security Process" information to the main website
Date: Mon, 27 Jan 2020 07:00:48 -0500	[thread overview]
Message-ID: <20200127070030-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a0b6986c-3732-9326-e383-675596dc61aa@redhat.com>

On Mon, Jan 27, 2020 at 11:00:29AM +0100, Thomas Huth wrote:
> On 23/01/2020 20.43, Eric Blake wrote:
> > On 1/23/20 11:11 AM, Thomas Huth wrote:
> >> One reporter of a security issue recently complained that it might not
> >> be the best idea to store our "Security Process" in the Wiki. Well, while
> >> the page in the Wiki is protected (so that only some few people can edit
> >> it), it is still possible that someone might find a bug in the Wiki
> >> software to alter the page contents...
> >> Anyway, it looks more trustworthy if we present the "Security Process"
> >> information in the static website instead. Thus this patch adds the
> >> information from the wiki to the Jekyll-based website now.
> >>
> >> Signed-off-by: Thomas Huth <thuth@redhat.com>
> >> ---
> >>   v2: Improved some sentences as suggested by Paolo
> >>
> > 
> >> +### Publication embargo
> >> +
> >> +As a security issue reported, that is not already publically disclosed
> > 
> > publicly
> > 
> >> +elsewhere, has an embargo date assigned and communicated to reporter.
> >> Embargo
> > 
> > Reads awkwardly. I'd suggest:
> > 
> > If a security issue is reported that is not already publicly disclosed,
> > an embargo date may be assigned and communicated to the reporter.
> 
> Ok, thanks, I've added your suggestions and pushed the changes now to
> the website.
> 
> To the people on CC: ... could someone please update the wiki page
> (https://wiki.qemu.org/SecurityProcess) to point to
> https://www.qemu.org/contribute/security-process/ instead? ... I don't
> have write access to that page, so I can not do that on my own.
> 
>  Thomas

Stefan I think you can do it right?

-- 
MST



  reply	other threads:[~2020-01-27 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 17:11 [qemu-web PATCH v2] Add "Security Process" information to the main website Thomas Huth
2020-01-23 17:14 ` Paolo Bonzini
2020-01-23 19:43 ` Eric Blake
2020-01-27 10:00   ` Thomas Huth
2020-01-27 12:00     ` Michael S. Tsirkin [this message]
2020-01-27 18:55     ` Paolo Bonzini

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=20200127070030-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=pjp@redhat.com \
    --cc=pmatouse@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.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 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.