From: P J P <ppandit@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Fam Zheng" <fam@euphon.net>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Ding, Ren" <rding@gatech.edu>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Zhao, Hanqing" <hanqing@gatech.edu>
Subject: Re: 回复: [PATCH 0/2] use unsigned type for MegasasState fields
Date: Wed, 13 May 2020 16:37:43 +0530 (IST) [thread overview]
Message-ID: <nycvar.YSQ.7.76.2005131624100.1451610@xnncv> (raw)
In-Reply-To: <4a9f8ae4-ef42-5a82-6d36-fb30f2878c6a@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
+-- On Tue, 12 May 2020, Philippe Mathieu-Daudé wrote --+
| The cover describes the bug as OOB, so I suppose this is a security issue.
| Now a 6 months embargo surprises me. I was expecting some period in a
| 30-90days range to be the default. However reading the 'Publication embargo'
| chapter on https://www.qemu.org/contribute/security-process/, it is only
| stated "Embargo periods will be negotiated by mutual agreement between
| members of the security team and other relevant parties to the problem."
| Shouldn't be a maximum upper limit on the embargo period? Are there QEMU
| security bugs embargoed for more than a year? That would be a shame.
Yes, some of these issue are old. We are working on the time-line details. We
have quite regular influx of CVE issues, which leads to long triage times for
some of them.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D
prev parent reply other threads:[~2020-05-13 11:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 10:57 [PATCH 0/2] use unsigned type for MegasasState fields P J P
2020-05-07 10:57 ` [PATCH 1/2] megasas: use unsigned type for reply_queue_head P J P
2020-05-12 18:52 ` Peter Maydell
2020-05-13 11:20 ` P J P
2020-05-07 10:57 ` [PATCH 2/2] megasas: use unsigned type for positive numeric fields P J P
2020-05-12 18:53 ` Peter Maydell
2020-05-13 11:22 ` P J P
2020-05-12 12:21 ` [PATCH 0/2] use unsigned type for MegasasState fields P J P
2020-05-12 13:42 ` Philippe Mathieu-Daudé
2020-05-12 18:37 ` P J P
2020-05-12 19:08 ` Alexander Bulekov
2020-05-12 19:48 ` Alexander Bulekov
2020-05-12 20:59 ` Philippe Mathieu-Daudé
2020-05-12 21:00 ` Alexander Bulekov
2020-05-13 11:13 ` P J P
2020-05-13 13:49 ` P J P
2020-05-13 14:20 ` Alexander Bulekov
2020-05-13 14:53 ` P J P
2020-05-13 17:08 ` Ding, Ren
2020-05-13 19:34 ` P J P
2020-05-13 14:53 ` Alexander Bulekov
[not found] ` <BN6PR07MB341283EBBF78F86AAA995382CABE0@BN6PR07MB3412.namprd07.prod.outlook.com>
2020-05-12 20:54 ` 回复: " Philippe Mathieu-Daudé
2020-05-13 11:07 ` P J P [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=nycvar.YSQ.7.76.2005131624100.1451610@xnncv \
--to=ppandit@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=hanqing@gatech.edu \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rding@gatech.edu \
/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).