From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 3.4.4 security fixes
Date: Mon, 27 Feb 2012 12:26:52 +0000 [thread overview]
Message-ID: <4F4B768C.40607@abpni.co.uk> (raw)
In-Reply-To: <1330344538.8557.280.camel@zakaz.uk.xensource.com>
On 27/02/2012 12:08, Ian Campbell wrote:
> On Mon, 2012-02-27 at 12:00 +0000, Jonathan Tripathy wrote:
>> " Security enhancements including CVE-2011-1583"
>>
>> However, the aforementioned CVE seems to only apply to other versions
>> of Xen (3.4.x is missing in the list of venerable software)
>>
>> While I'm obviously happy that the latest release is free of this bug,
>> can someone please shed some light on how this bug was fixed in 3.4.4,
>> when it wasn't supposed to be present in the first place in 3.4.3?
> Given that 3.3 and 4.0 were vulnerable I think this is simply a case of
> 3.4 being accidentally omitted from the list.
>
> Ian.
>
>
Thanks for the reply, Ian.
Any ideas on what other security issues were fixed?
Thanks
prev parent reply other threads:[~2012-02-27 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 12:00 Xen 3.4.4 security fixes Jonathan Tripathy
2012-02-27 12:08 ` Ian Campbell
2012-02-27 12:26 ` Jonathan Tripathy [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=4F4B768C.40607@abpni.co.uk \
--to=jonnyt@abpni.co.uk \
--cc=Ian.Campbell@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.