All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org,
	joshua.g.lock@intel.com, akuster808@gmail.com
Subject: [PATCH 00/21][Fido v3] pull request
Date: Sat,  6 Feb 2016 15:14:41 -0800	[thread overview]
Message-ID: <cover.1454800360.git.akuster@mvista.com> (raw)

From: Armin Kuster <akuster@mvista.com>

forgot to append a change to bind recipe.

This includes a miss fire on the glibc request plus many others.
This supersedes the last tow fido pull request

The following changes since commit 9845a542a76156adb5aef6fd33ad5bc5777acf64:

  openssh: CVE-2016-077x (2016-01-20 17:08:30 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib akuster/fido_cve_fixes
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/fido_cve_fixes

Armin Kuster (18):
  glibc: CVE-2015-8777
  glibc: CVE-2015-8779
  glibc: CVE-2015-9761
  glibc: CVE-2015-8776
  openssl: Security fix CVE-2015-3197
  openssl: Security fix CVE-2016-0701
  qemu: Security fix CVE-2015-8504
  qemu: Security fix CVE-2015-7504
  qemu: Security fix CVE-2015-7512
  qemu: Security fix CVE-2015-8345
  qemu: Security fix CVE-2016-1568
  qemu: Security fix CVE-2015-7295
  tzcode: update to 2016a
  tzdata: update to 2016a
  dpkg: Security fix CVE-2015-0860
  libxml2: Security fix CVE-2015-8241
  libxml2: Security fix CVE-2015-8710
  bind: Security fix CVE-2015-8704

Paul Eggleton (1):
  tzdata: reinstate changes reverted in 2014c upgrade

Wenzong Fan (2):
  subversion: fix CVE-2015-3184
  subversion: fix CVE-2015-3187

 .../bind/bind/CVE-2015-8704.patch                  |   29 +
 meta/recipes-connectivity/bind/bind_9.9.5.bb       |    1 +
 .../openssl/openssl/CVE-2015-3197.patch            |   63 +
 .../openssl/openssl/CVE-2016-0701_1.patch          |  102 +
 .../openssl/openssl/CVE-2016-0701_2.patch          |  156 ++
 .../recipes-connectivity/openssl/openssl_1.0.2d.bb |    3 +
 meta/recipes-core/glibc/glibc/CVE-2015-8776.patch  |  155 ++
 meta/recipes-core/glibc/glibc/CVE-2015-8777.patch  |  122 ++
 meta/recipes-core/glibc/glibc/CVE-2015-8779.patch  |  262 +++
 .../recipes-core/glibc/glibc/CVE-2015-9761_1.patch | 1039 ++++++++++
 .../recipes-core/glibc/glibc/CVE-2015-9761_2.patch |  388 ++++
 meta/recipes-core/glibc/glibc_2.21.bb              |    5 +
 meta/recipes-core/libxml/libxml2.inc               |    2 +
 .../libxml/libxml2/CVE-2015-8241.patch             |   40 +
 .../libxml/libxml2/CVE-2015-8710.patch             |   71 +
 .../recipes-devtools/dpkg/dpkg/CVE-2015-0860.patch |   53 +
 meta/recipes-devtools/dpkg/dpkg_1.17.21.bb         |    1 +
 .../qemu/qemu/CVE-2015-7295_1.patch                |   63 +
 .../qemu/qemu/CVE-2015-7295_2.patch                |   58 +
 .../qemu/qemu/CVE-2015-7295_3.patch                |   52 +
 .../recipes-devtools/qemu/qemu/CVE-2015-7504.patch |   56 +
 .../recipes-devtools/qemu/qemu/CVE-2015-7512.patch |   44 +
 .../recipes-devtools/qemu/qemu/CVE-2015-8345.patch |   73 +
 .../recipes-devtools/qemu/qemu/CVE-2015-8504.patch |   51 +
 .../recipes-devtools/qemu/qemu/CVE-2016-1568.patch |   46 +
 meta/recipes-devtools/qemu/qemu_2.2.0.bb           |    8 +
 .../subversion-CVE-2015-3184.patch                 | 2082 ++++++++++++++++++++
 .../subversion-CVE-2015-3187.patch                 |  346 ++++
 .../subversion/subversion_1.8.11.bb                |    2 +
 ...code-native_2015g.bb => tzcode-native_2016a.bb} |   16 +-
 meta/recipes-extended/tzdata/tzdata.inc            |    5 +-
 .../tzdata/{tzdata_2015g.bb => tzdata_2016a.bb}    |   10 +-
 32 files changed, 5389 insertions(+), 15 deletions(-)
 create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2015-8704.patch
 create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2015-3197.patch
 create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-0701_1.patch
 create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-0701_2.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-8776.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-8777.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-8779.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-9761_1.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-9761_2.patch
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2015-8241.patch
 create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2015-8710.patch
 create mode 100644 meta/recipes-devtools/dpkg/dpkg/CVE-2015-0860.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-7295_1.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-7295_2.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-7295_3.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-7504.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-7512.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-8345.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2015-8504.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-1568.patch
 create mode 100644 meta/recipes-devtools/subversion/subversion-1.8.11/subversion-CVE-2015-3184.patch
 create mode 100644 meta/recipes-devtools/subversion/subversion-1.8.11/subversion-CVE-2015-3187.patch
 rename meta/recipes-extended/tzcode/{tzcode-native_2015g.bb => tzcode-native_2016a.bb} (40%)
 rename meta/recipes-extended/tzdata/{tzdata_2015g.bb => tzdata_2016a.bb} (96%)

-- 
2.3.5



             reply	other threads:[~2016-02-06 23:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 23:14 Armin Kuster [this message]
2016-02-06 23:14 ` [PATCH 01/21] glibc: CVE-2015-8777 Armin Kuster
2016-02-06 23:14 ` [PATCH 02/21] glibc: CVE-2015-8779 Armin Kuster
2016-02-06 23:14 ` [PATCH 03/21] glibc: CVE-2015-9761 Armin Kuster
2016-02-06 23:14 ` [PATCH 04/21] glibc: CVE-2015-8776 Armin Kuster
2016-02-06 23:14 ` [PATCH 05/21] openssl: Security fix CVE-2015-3197 Armin Kuster
2016-02-06 23:14 ` [PATCH 06/21] openssl: Security fix CVE-2016-0701 Armin Kuster
2016-02-06 23:14 ` [PATCH 07/21] subversion: fix CVE-2015-3184 Armin Kuster
2016-02-06 23:14 ` [PATCH 08/21] subversion: fix CVE-2015-3187 Armin Kuster
2016-02-06 23:14 ` [PATCH 09/21] qemu: Security fix CVE-2015-8504 Armin Kuster
2016-02-06 23:14 ` [PATCH 10/21] qemu: Security fix CVE-2015-7504 Armin Kuster
2016-02-06 23:14 ` [PATCH 11/21] qemu: Security fix CVE-2015-7512 Armin Kuster
2016-02-06 23:14 ` [PATCH 12/21] qemu: Security fix CVE-2015-8345 Armin Kuster
2016-02-06 23:14 ` [PATCH 13/21] qemu: Security fix CVE-2016-1568 Armin Kuster
2016-02-06 23:14 ` [PATCH 14/21] qemu: Security fix CVE-2015-7295 Armin Kuster
2016-02-06 23:14 ` [PATCH 15/21] tzcode: update to 2016a Armin Kuster
2016-02-06 23:14 ` [PATCH 16/21] tzdata: " Armin Kuster
2016-02-06 23:14 ` [PATCH 17/21] tzdata: reinstate changes reverted in 2014c upgrade Armin Kuster
2016-02-06 23:14 ` [PATCH 18/21] dpkg: Security fix CVE-2015-0860 Armin Kuster
2016-02-06 23:15 ` [PATCH 19/21] libxml2: Security fix CVE-2015-8241 Armin Kuster
2016-02-06 23:15 ` [PATCH 20/21] libxml2: Security fix CVE-2015-8710 Armin Kuster
2016-02-06 23:15 ` [PATCH 21/21] bind: Security fix CVE-2015-8704 Armin Kuster
2016-02-08 15:29 ` [PATCH 00/21][Fido v3] pull request Joshua G Lock

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.1454800360.git.akuster@mvista.com \
    --to=akuster808@gmail.com \
    --cc=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.