From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: xen-devel@lists.xen.org, keith.coleman@n2servers.com
Subject: Re: Xen 3.4.x Backports
Date: Thu, 14 Jun 2012 11:37:34 +0100 [thread overview]
Message-ID: <4FD9BEEE.6020504@abpni.co.uk> (raw)
In-Reply-To: <CAH4C7zH9_e6ObQH46iuQd8Ms4OJUBGcYDV5PR2GG5_UxD17sEQ@mail.gmail.com>
On 01/03/2012 11:40, Keith Coleman wrote:
> On Wed, Feb 29, 2012 at 4:53 AM, Ian Campbell<Ian.Campbell@citrix.com> wrote:
>> On Tue, 2012-02-28 at 23:36 +0000, Jonathan Tripathy wrote:
>>> Hi Keith,
> Jonathan,
>
> Thank you for bringing up these issues. I will resolve them.
>
>> On a related note it would be very useful if
>> http://wiki.xen.org/wiki/Security_Announcements could be updated when
>> security fixes corresponding to Xen.org security vulnerability
>> disclosures are added to the 3.4 branch. Keith, can you do that? If not
>> then if you drop me a line each time I'll take care of it for you.
>>
> Certainly!
>
>
> --
> Keith Coleman
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
Hi Keith,
Is there any update regarding the issue of backporting a few patches, as
per my post from February? The CVEs in question are:
CVE-2011-2901
CVE-2011-1898
CVE-2012-0029
CVE-2011-1166
I'm also guessing that 3.4.5 will be released very soon, due to the
recent CVEs (http://lists.xen.org/archives/html/xen-announce/2012-06/) ?
I appreciate your time
Many Thanks
Jonathan
prev parent reply other threads:[~2012-06-14 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 23:36 Xen 3.4.x Backports Jonathan Tripathy
2012-02-28 23:47 ` Fajar A. Nugraha
2012-02-28 23:51 ` Jonathan Tripathy
2012-02-28 23:56 ` Fajar A. Nugraha
2012-02-29 9:53 ` Ian Campbell
2012-03-01 11:40 ` Keith Coleman
2012-06-14 10:37 ` 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=4FD9BEEE.6020504@abpni.co.uk \
--to=jonnyt@abpni.co.uk \
--cc=keith.coleman@n2servers.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 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).