Fido-next libxml2 sercurity fixes
cover Fido-next libxml2 sercurity fixes
Please consider these libxml2 fixes for fido-next
The following changes since commit c9f0a99050ec0050f0dbcd55d0cd2ab18848113f:
build-appliance-image: Update to fido head revision (2016-05-12 13:14:51 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akuster/fido-next
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/fido-next
Armin Kuster (15):
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
.../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 + 17 files changed, 3186 insertions(+) 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
Signature · 1 line
2.3.5