From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/xen: security bump to version 4.13.1
Date: Sun, 31 May 2020 10:04:58 +0200 [thread overview]
Message-ID: <20200531080458.GX8737@scaer> (raw)
In-Reply-To: <20200530122532.3477185-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2020-05-30 14:25 +0200, Fabrice Fontaine spake thusly:
> - Fix CVE-2020-11739: An issue was discovered in Xen through 4.13.x,
[--SNIP--]
> - Fix CVE-2020-11740: An issue was discovered in xenoprof in Xen through
[--SNIP--]
> - Fix CVE-2020-11741: An issue was discovered in xenoprof in Xen through
[--SNIP--]
> - Fix CVE-2020-11742: An issue was discovered in Xen through 4.13.x,
[--SNIP--]
> - Fix CVE-2020-11743: An issue was discovered in Xen through 4.13.x,
[--SNIP--]
> https://xenproject.org/downloads/xen-project-archives/xen-project-4-13-series/xen-project-4-13-1
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Applied to master, thank.
Regards,
Yann E. MORIN.
> ---
> package/xen/xen.hash | 2 +-
> package/xen/xen.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/xen/xen.hash b/package/xen/xen.hash
> index 4224924652..ab5f9d9083 100644
> --- a/package/xen/xen.hash
> +++ b/package/xen/xen.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 c69ae21b2ddeaf25532a81a448fcc6a218bc56f93c8907b2d416b2d4339c0afe xen-4.13.0.tar.gz
> +sha256 b97ce363e55b12c992063f4466c43cba0a6386ceb7a747b4dc670311f337ef01 xen-4.13.1.tar.gz
> sha256 36b91794c6d4a678137c70c41e384c03b552c7efba82c0d73e6be842e41ab3d3 COPYING
> diff --git a/package/xen/xen.mk b/package/xen/xen.mk
> index fa49f5996b..15742b5127 100644
> --- a/package/xen/xen.mk
> +++ b/package/xen/xen.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -XEN_VERSION = 4.13.0
> +XEN_VERSION = 4.13.1
> XEN_SITE = https://downloads.xenproject.org/release/xen/$(XEN_VERSION)
> XEN_LICENSE = GPL-2.0
> XEN_LICENSE_FILES = COPYING
> --
> 2.26.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-05-31 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 12:25 [Buildroot] [PATCH 1/1] package/xen: security bump to version 4.13.1 Fabrice Fontaine
2020-05-31 8:04 ` Yann E. MORIN [this message]
2020-06-02 6:14 ` Peter Korsgaard
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=20200531080458.GX8737@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.