Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/7] [jethro] Consolidated pull
Date: Wed, 27 Jan 2016 01:35:20 -0800	[thread overview]
Message-ID: <cover.1453877220.git.liezhi.yang@windriver.com> (raw)

The following changes since commit 8ce8f62b22b1e20db0f62d7bd8246738147d5f2e:

  nativesdk-buildtools-perl-dummy: Bump PR (2016-01-21 16:21:14 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/jethro-next
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/jethro-jext

Armin Kuster (5):
  glibc: CVE-2015-8777.patch
  glibc: CVE-2015-8779
  glibc: CVE-2015-9761
  glibc: CVE-2015-8776
  openssh: CVE-2016-1907

Derek Straka (1):
  bind: CVE-2015-8704 and CVE-2015-8705

Mariano Lopez (1):
  rpmresolve.c: Fix unfreed pointers that keep DB opened

 .../bind/bind/CVE-2015-8704.patch                  |   28 +
 .../bind/bind/CVE-2015-8705.patch                  |   44 +
 meta/recipes-connectivity/bind/bind_9.10.2-P4.bb   |    2 +
 .../openssh/openssh/CVE-2016-1907_2.patch          |   65 ++
 .../openssh/openssh/CVE-2016-1907_3.patch          |  329 +++++++
 .../openssh/CVE-2016-1907_upstream_commit.patch    |   33 +
 meta/recipes-connectivity/openssh/openssh_7.1p2.bb |    5 +-
 meta/recipes-core/glibc/glibc/CVE-2015-8776.patch  |  155 +++
 meta/recipes-core/glibc/glibc/CVE-2015-8777.patch  |  123 +++
 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 |  385 ++++++++
 meta/recipes-core/glibc/glibc_2.22.bb              |    5 +
 meta/recipes-devtools/rpm/rpmresolve/rpmresolve.c  |   10 +-
 14 files changed, 2480 insertions(+), 5 deletions(-)
 create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2015-8704.patch
 create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2015-8705.patch
 create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-1907_2.patch
 create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-1907_3.patch
 create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-1907_upstream_commit.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

-- 
1.7.9.5



             reply	other threads:[~2016-01-27  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  9:35 Robert Yang [this message]
2016-01-27  9:35 ` [PATCH 1/7] glibc: CVE-2015-8777.patch Robert Yang
2016-01-27  9:35 ` [PATCH 2/7] glibc: CVE-2015-8779 Robert Yang
2016-01-27  9:35 ` [PATCH 3/7] glibc: CVE-2015-9761 Robert Yang
2016-01-27  9:35 ` [PATCH 4/7] glibc: CVE-2015-8776 Robert Yang
2016-01-27  9:35 ` [PATCH 5/7] openssh: CVE-2016-1907 Robert Yang
2016-01-27  9:35 ` [PATCH 6/7] rpmresolve.c: Fix unfreed pointers that keep DB opened Robert Yang
2016-01-27  9:35 ` [PATCH 7/7] bind: CVE-2015-8704 and CVE-2015-8705 Robert Yang

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.1453877220.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox