From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [Fido][PATCH 00/18] Updates for fido
Date: Fri, 12 Aug 2016 13:28:11 +0100 [thread overview]
Message-ID: <cover.1471004470.git.joshua.g.lock@intel.com> (raw)
Please consider the following patches for the fido branch.
They have been queued in my joshuagl/fido-next branch of openembedded-core-contrib for too long, apologies to the authors and submitters.
Regards,
Joshua
The following changes since commit 511ea0fcc9c238ad8e3b3089ec2bcf82bb1ecc77:
build-appliance-image: Update to fido head revision (2016-05-12 13:14:48 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/fido-next
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/fido-next
Armin Kuster (17):
tzcode: update to 2016e
tzdata: update to 2016e
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
Roy Li (1):
systemd: re-enable mount propagation for udevd
.../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 | 18 +
...dev-re-enable-mount-propagation-for-udevd.patch | 29 +
meta/recipes-core/systemd/systemd_219.bb | 1 +
...code-native_2016d.bb => tzcode-native_2016e.bb} | 9 +-
.../tzdata/{tzdata_2016d.bb => tzdata_2016e.bb} | 4 +-
21 files changed, 3223 insertions(+), 6 deletions(-)
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
create mode 100644 meta/recipes-core/systemd/systemd/udev-re-enable-mount-propagation-for-udevd.patch
rename meta/recipes-extended/tzcode/{tzcode-native_2016d.bb => tzcode-native_2016e.bb} (67%)
rename meta/recipes-extended/tzdata/{tzdata_2016d.bb => tzdata_2016e.bb} (98%)
--
2.7.4
reply other threads:[~2016-08-12 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1471004470.git.joshua.g.lock@intel.com \
--to=joshua.g.lock@intel.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.