Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [zeus][PATCH 00/10] zeus -next review
Date: Wed,  4 Dec 2019 21:31:41 +0800	[thread overview]
Message-ID: <cover.1575465665.git.anuj.mittal@intel.com> (raw)

Next set of patches for zeus. Please let me know if there are any
comments.

Thanks,

Anuj

The following changes since commit 5d50b0549e5d91cb3072dada0e33a43dfb9e2071:

  bitbake: runqueue.py: not show warning for deferred multiconfig task (2019-11-29 11:26:18 +0000)

are available in the Git repository at:

  git://push.yoctoproject.org/poky-contrib anujm/zeus

Adrian Bunk (1):
  bind: Whitelist CVE-2019-6470

Anuj Mittal (4):
  ghostscript: fix for CVE-2019-14811 is same as CVE-2019-14813
  nasm: fix CVE-2019-14248
  glibc: fix CVE-2019-19126
  libarchive: fix CVE-2019-19221

Christopher Larson (1):
  dosfstools: fix CP437 error from `dosfsck -l`

Hongxu Jia (1):
  go: fix CVE-2019-17596

Ross Burton (1):
  libsoup-2.4: upgrade to 2.66.4

Stefan Ghinea (1):
  ghostscript: CVE-2019-14869

Vinay Kumar (1):
  gdb: Fix CVE-2019-1010180

 .../bind/bind_9.11.5-P4.bb                    |   4 +
 .../glibc/glibc/CVE-2019-19126.patch          |  32 +++++
 meta/recipes-core/glibc/glibc_2.30.bb         |   1 +
 .../dosfstools/dosfstools_4.1.bb              |   3 +
 meta/recipes-devtools/gdb/gdb-8.3.1.inc       |   1 +
 .../gdb/gdb/CVE-2019-1010180.patch            | 132 ++++++++++++++++++
 meta/recipes-devtools/go/go-1.12.inc          |   1 +
 .../go/go-1.12/0010-fix-CVE-2019-17596.patch  |  42 ++++++
 .../nasm/nasm/CVE-2019-14248.patch            |  43 ++++++
 meta/recipes-devtools/nasm/nasm_2.14.02.bb    |   1 +
 .../ghostscript/CVE-2019-14811-0001.patch     |   1 +
 .../ghostscript/CVE-2019-14869-0001.patch     |  70 ++++++++++
 .../ghostscript/ghostscript_9.27.bb           |   1 +
 .../libarchive/CVE-2019-19221.patch           | 101 ++++++++++++++
 .../libarchive/libarchive_3.4.0.bb            |   1 +
 ...up-2.4_2.66.2.bb => libsoup-2.4_2.66.4.bb} |   6 +-
 16 files changed, 437 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2019-19126.patch
 create mode 100644 meta/recipes-devtools/gdb/gdb/CVE-2019-1010180.patch
 create mode 100644 meta/recipes-devtools/go/go-1.12/0010-fix-CVE-2019-17596.patch
 create mode 100644 meta/recipes-devtools/nasm/nasm/CVE-2019-14248.patch
 create mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2019-14869-0001.patch
 create mode 100644 meta/recipes-extended/libarchive/libarchive/CVE-2019-19221.patch
 rename meta/recipes-support/libsoup/{libsoup-2.4_2.66.2.bb => libsoup-2.4_2.66.4.bb} (89%)

-- 
2.21.0



             reply	other threads:[~2019-12-04 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 13:31 Anuj Mittal [this message]
2019-12-04 13:31 ` [zeus][PATCH 01/10] ghostscript: CVE-2019-14869 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 02/10] gdb: Fix CVE-2019-1010180 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 03/10] bind: Whitelist CVE-2019-6470 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 04/10] go: fix CVE-2019-17596 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 05/10] libsoup-2.4: upgrade to 2.66.4 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 06/10] ghostscript: fix for CVE-2019-14811 is same as CVE-2019-14813 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 07/10] nasm: fix CVE-2019-14248 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 08/10] glibc: fix CVE-2019-19126 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 09/10] libarchive: fix CVE-2019-19221 Anuj Mittal
2019-12-04 13:31 ` [zeus][PATCH 10/10] dosfstools: fix CP437 error from `dosfsck -l` Anuj Mittal
2019-12-04 14:01 ` ✗ patchtest: failure for zeus -next review Patchwork

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