From: Don Slutz <dslutz@verizon.com>
To: Major Hayden <major.hayden@rackspace.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Earlier embargoed pre-disclosure without patches
Date: Wed, 27 May 2015 10:07:42 -0400 [thread overview]
Message-ID: <5565CFAE.9030001@one.verizon.com> (raw)
In-Reply-To: <6c74b216b5fe44778d98af0afe661e7b@543881-IEXCH01.ror-uc.rackspace.com>
[-- Attachment #1.1: Type: text/plain, Size: 682 bytes --]
On 05/26/15 16:34, Major Hayden wrote:
> On 05/26/2015 11:50 AM, Stefano Stabellini wrote:
>> I would go for:
>
>> In the event that public disclosure is less than 15 days away, we will
>> send a draft with information about the vulnerability to the
>> pre-disclosure list as soon as possible, even if patches have not yet
>> been written or tested. An updated draft will be sent to the
>> pre-disclosure list once patches become available.
>
> No objections here. +1
>
>
Also looks good to me. +1
-Don Slutz
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-05-27 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 13:03 Earlier embargoed pre-disclosure without patches Major Hayden
2015-05-22 7:40 ` Jan Beulich
2015-05-22 13:14 ` Major Hayden
2015-05-22 14:04 ` Jan Beulich
2015-05-22 14:12 ` Major Hayden
2015-05-26 12:15 ` Stefano Stabellini
2015-05-26 15:38 ` Major Hayden
2015-05-26 16:34 ` Stefano Stabellini
2015-05-26 20:34 ` Major Hayden
2015-05-27 14:07 ` Don Slutz [this message]
2015-05-27 17:47 ` Lars Kurth
2015-05-30 19:26 ` Major Hayden
2015-05-27 11:39 ` Ian Campbell
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=5565CFAE.9030001@one.verizon.com \
--to=dslutz@verizon.com \
--cc=JBeulich@suse.com \
--cc=major.hayden@rackspace.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.