From: Tim Deegan <tim@xen.org>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: ian.jackson@citrix.com, security@xen.org,
ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: Xen Security Advisory 11 (CVE-2012-3433) - HVM destroy p2m host DoS (Xen.org security team)
Date: Thu, 9 Aug 2012 18:15:34 +0100 [thread overview]
Message-ID: <20120809171534.GA20963@ocelot.phlegethon.org> (raw)
In-Reply-To: <a70961e11bf7f64f32519d3d5ef85fc6.squirrel@webmail.lagarcavilla.org>
At 09:30 -0700 on 09 Aug (1344504612), Andres Lagar-Cavilla wrote:
> I realize Gridcentric is neither a service provider, nor a "big vendor",
> and therefore not on the pre-disclosure list.
>
> However, this is a bug on which we have first-hand knowledge and ability
> to immediately mitigate. In fact, I wrote equivalent code for 4.2/unstable
> months ago.
For which, thank you -- your patch, and the description of it at the
time, made drafting this response much easier!
> I ignored the xen-devel discussion on pre-disclosure list (my bad), but
> understand now that there may be some use to Gridcentric being in that
> list.
If you mean helping draft a fix, being on the pre-disclosure list
wouldn't have made a difference (unless you see a problem with the
published fix), as that was all done before pre-disclosure.
As to whether GridCentric ought to be on the pre-disclosure list as a
downstream vendor, now is definitely the time to speak up in the
discussion of what the new policy should be.
Cheers,
Tim.
prev parent reply other threads:[~2012-08-09 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.10477.1344525712.1399.xen-devel@lists.xen.org>
2012-08-09 16:30 ` Xen Security Advisory 11 (CVE-2012-3433) - HVM destroy p2m host DoS (Xen.org security team) Andres Lagar-Cavilla
2012-08-09 16:40 ` George Dunlap
2012-08-09 16:44 ` Andres Lagar-Cavilla
2012-08-09 17:15 ` Tim Deegan [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=20120809171534.GA20963@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=andres@lagarcavilla.org \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=security@xen.org \
--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 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).