From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/5] Pull request (cover letter only)
Date: Mon, 23 Nov 2020 15:07:12 -1000 [thread overview]
Message-ID: <cover.1606179985.git.steve@sakoman.com> (raw)
The following changes since commit 84e1a32096db9deb98d282a652beec95dbfe80f1:
python3: add ldconfig rdepends for python3-ctypes (2020-11-17 07:34:27 -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
Lee Chee Yang (5):
libproxy: fix CVE-2020-26154
bison: update to 3.5.4 for CVE-2020-14150
python3: whitelist CVE-2020-15523
python3: fix CVE-2020-27619
qemu: fix CVE-2020-24352
.../bison/{bison_3.5.3.bb => bison_3.5.4.bb} | 2 +-
.../python/python3/CVE-2020-27619.patch | 70 +++++++++++++
meta/recipes-devtools/python/python3_3.8.2.bb | 4 +
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2020-24352.patch | 52 ++++++++++
.../libproxy/libproxy/CVE-2020-26154.patch | 98 +++++++++++++++++++
.../libproxy/libproxy_0.4.15.bb | 1 +
7 files changed, 227 insertions(+), 1 deletion(-)
rename meta/recipes-devtools/bison/{bison_3.5.3.bb => bison_3.5.4.bb} (94%)
create mode 100644 meta/recipes-devtools/python/python3/CVE-2020-27619.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-24352.patch
create mode 100644 meta/recipes-support/libproxy/libproxy/CVE-2020-26154.patch
--
2.17.1
next reply other threads:[~2020-11-24 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 1:07 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-08 0:20 [OE-core][dunfell 0/5] Pull request (cover letter only) Steve Sakoman
2020-10-20 17:35 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.1606179985.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.