From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/2] Pull request (cover letter only)
Date: Mon, 2 Nov 2020 17:07:18 -1000 [thread overview]
Message-ID: <cover.1604372711.git.steve@sakoman.com> (raw)
The following changes since commit 8a367cbbf092339a8c82c680a2565567b594b6c6:
glib-2.0: fix parsing of slim encoded tzdata (2020-10-26 15:06:51 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Alexander Kanavin (1):
nasm: update 2.14.02 -> 2.15.03 for CVE fixes
Steve Sakoman (1):
qemu: fix CVE-2019-20175
.../nasm/nasm/0001-stdlib-Add-strlcat.patch | 28 ++--
.../0002-Add-debug-prefix-map-option.patch | 129 +++++++-----------
.../nasm/nasm/CVE-2018-19755.patch | 116 ----------------
.../nasm/nasm/CVE-2019-14248.patch | 43 ------
.../nasm/{nasm_2.14.02.bb => nasm_2.15.03.bb} | 10 +-
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2019-20175.patch | 94 +++++++++++++
7 files changed, 161 insertions(+), 260 deletions(-)
delete mode 100644 meta/recipes-devtools/nasm/nasm/CVE-2018-19755.patch
delete mode 100644 meta/recipes-devtools/nasm/nasm/CVE-2019-14248.patch
rename meta/recipes-devtools/nasm/{nasm_2.14.02.bb => nasm_2.15.03.bb} (56%)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2019-20175.patch
--
2.17.1
next reply other threads:[~2020-11-03 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 3:07 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-04 19:31 [OE-core][dunfell 0/2] Pull request (cover letter only) Steve Sakoman
2022-10-05 3:30 ` Tim Orling
2021-03-11 15:27 Steve Sakoman
2020-10-09 0:17 Steve Sakoman
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.1604372711.git.steve@sakoman.com \
--to=steve@sakoman.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.