From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Armin Kuster <akuster@mvista.com>
Subject: Re: [PATCH 00/17] Jethro-next security fixes
Date: Mon, 25 Jul 2016 12:27:32 -0700 [thread overview]
Message-ID: <57966824.5020609@gmail.com> (raw)
In-Reply-To: <cover.1468111537.git.akuster@mvista.com>
Ping
On 07/09/2016 06:08 PM, Armin Kuster wrote:
> From: Armin Kuster <akuster@mvista.com>
>
> Please consider these changes for jethro-next.
>
> The libxml2 changes don't affect Master nor krogoth.
> Glibc changes have been sent for Master and soon for Krogoth.
>
> The following changes since commit 118380bc5d01e52b5edc574abb4176f6e70a54a6:
>
> documentation: Updated date in the manual revision tables. (2016-06-21 12:59:47 +0100)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib akuster/jethro-next
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/jethro-next
>
> Armin Kuster (17):
> glibc: Security Fix for CVE-2016-3706
> glibc: Security fix for CVE-2016-4429
> libxml2: Security fix for CVE-2016-1762
> libxml2: Security fix for CVE-2016-3705
> libxml2: Security fix for CVE-2016-1834.patch
> libxml2: Security fix for CVE-2016-4483.patch
> libxml2: Security fix for CVE-2016-1840
> libxml2: Security fix for CVE-2016-1838
> libxml2: Security fix for CVE-2016-1839
> libxml2: Security fix for CVE-2016-1836
> libxml2: Security fix for CVE-2016-4449
> libxml2: Security fix for CVE-2016-1837
> libxml2: Security fix for CVE-2016-1835
> libxml2: Security fix for CVE-2016-1833
> libxml2: Security fix for CVE-2016-3627
> libxml2: Security fix for CVE-2016-4447
> libxml2: Security fix for CVE-2016-4448
>
> meta/recipes-core/glibc/glibc/CVE-2016-3706.patch | 226 +++++
> meta/recipes-core/glibc/glibc/CVE-2016-4429.patch | 89 ++
> meta/recipes-core/glibc/glibc_2.22.bb | 2 +
> .../libxml/libxml2/CVE-2016-1762.patch | 84 ++
> .../libxml/libxml2/CVE-2016-1833.patch | 368 +++++++
> .../libxml/libxml2/CVE-2016-1834.patch | 55 +
> .../libxml/libxml2/CVE-2016-1835.patch | 95 ++
> .../libxml/libxml2/CVE-2016-1836.patch | 443 ++++++++
> .../libxml/libxml2/CVE-2016-1837.patch | 143 +++
> .../libxml/libxml2/CVE-2016-1838.patch | 96 ++
> .../libxml/libxml2/CVE-2016-1839.patch | 127 +++
> .../libxml/libxml2/CVE-2016-1840.patch | 37 +
> .../libxml/libxml2/CVE-2016-3627.patch | 64 ++
> .../libxml/libxml2/CVE-2016-3705.patch | 71 ++
> .../libxml/libxml2/CVE-2016-4447.patch | 208 ++++
> .../libxml/libxml2/CVE-2016-4448_1.patch | 1067 ++++++++++++++++++++
> .../libxml/libxml2/CVE-2016-4448_2.patch | 208 ++++
> .../libxml/libxml2/CVE-2016-4449.patch | 47 +
> .../libxml/libxml2/CVE-2016-4483.patch | 55 +
> meta/recipes-core/libxml/libxml2_2.9.2.bb | 17 +
> 20 files changed, 3502 insertions(+)
> create mode 100644 meta/recipes-core/glibc/glibc/CVE-2016-3706.patch
> create mode 100644 meta/recipes-core/glibc/glibc/CVE-2016-4429.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1762.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1833.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1834.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1835.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1836.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1837.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1838.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1839.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-1840.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-3627.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-3705.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-4447.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-4448_1.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-4448_2.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-4449.patch
> create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2016-4483.patch
>
prev parent reply other threads:[~2016-07-25 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 1:08 [PATCH 00/17] Jethro-next security fixes Armin Kuster
2016-07-25 19:27 ` akuster808 [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=57966824.5020609@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.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.