All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: AL13N <alien@rmail.be>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen security issues
Date: Sun, 14 Apr 2013 23:05:19 +0100	[thread overview]
Message-ID: <516B281F.8020800@citrix.com> (raw)
In-Reply-To: <8568660.6LpFT92G3A@localhost>

On 14/04/2013 19:35, AL13N wrote:
> Op zondag 14 april 2013 11:15:03 schreef Ian Campbell:
>> On Sun, 2013-04-14 at 08:05 +0100, AL13N wrote:
>>> I'm the Mageia maintainer and i'm a bit behind on patching CVE-* .
>>>
>>> can anyone help me find out which of these are actually applicable for
>>> 4.1.2?
>> You can find a list of the already public Xen security announcements,
>> with CVE numbers and links to advisories, patches etc at:
>>
>> http://wiki.xen.org/wiki/Security_Announcements
> the problem is not finding the patches :-)
>
> the problem is which in those huge lists are actually applicable to that 
> specific version: xen-4.2.1
>
> or more, which aren't applicable :-).


http://wiki.xen.org/wiki/Xen_4.2_Release_Notes

Xen 4.2 was released on 17 Sept 2012.  XSA-19 and earlier where older
than that, so are not applicable.  XSA-20 and newer all specifically
refer to xen-4.2-testing and whether it is vulnerable or not.

Although now I note that you might have transposed 4.1.2.

So the 4.1 release notes puts 4.1.2 on 21 Oct 2011.  However, I would
highly recomend moving forwards to 4.1.4 or even newer.  4.1.x is in
maintenance now and is only receiving bugfixes, but being OS software,
there is still a steady stream of bugfixes being backported.

~Andrew

  reply	other threads:[~2013-04-14 22:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14  7:05 Xen security issues AL13N
2013-04-14 10:15 ` Ian Campbell
2013-04-14 18:35   ` AL13N
2013-04-14 22:05     ` Andrew Cooper [this message]
2013-04-15 10:44       ` AL13N
2013-04-15  8:03     ` M A Young
2013-04-15  8:25     ` 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=516B281F.8020800@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=alien@rmail.be \
    --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.