From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 0/7] Pull request (cover letter only)
Date: Wed, 18 Aug 2021 16:38:06 +0800 [thread overview]
Message-ID: <cover.1629275770.git.anuj.mittal@intel.com> (raw)
Please merge these changes.
Thanks,
Anuj
The following changes since commit 49868162a1a1d088fbaabeffcc2debcbfc17b026:
nettle: update 3.7.2 -> 3.7.3 (2021-08-09 10:19:38 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Armin Kuster (1):
gnutls: Enable seccomp if FEATURE is set
Khem Raj (1):
gnutls: Point to staging area for finding seccomp libs and includes
Sakib Sajal (3):
qemu: fix CVE-2021-3582
qemu: fix CVE-2021-3607
qemu: fix CVE-2021-3608
Vinay Kumar (1):
glibc: Fix CVE-2021-35942
wangmy (1):
gnutls: upgrade 3.7.1 -> 3.7.2
.../glibc/glibc/CVE-2021-35942.patch | 44 +++++++++++++++++
meta/recipes-core/glibc/glibc_2.33.bb | 1 +
meta/recipes-devtools/qemu/qemu.inc | 3 ++
.../qemu/qemu/CVE-2021-3582.patch | 47 +++++++++++++++++++
.../qemu/qemu/CVE-2021-3607.patch | 43 +++++++++++++++++
.../qemu/qemu/CVE-2021-3608.patch | 43 +++++++++++++++++
.../{gnutls_3.7.1.bb => gnutls_3.7.2.bb} | 6 +--
7 files changed, 184 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2021-35942.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3582.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3607.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3608.patch
rename meta/recipes-support/gnutls/{gnutls_3.7.1.bb => gnutls_3.7.2.bb} (89%)
--
2.31.1
reply other threads:[~2021-08-18 8:38 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.1629275770.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 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.