From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/13] Pull request (cover letter only)
Date: Wed, 23 Mar 2022 12:28:20 -1000 [thread overview]
Message-ID: <cover.1648074246.git.steve@sakoman.com> (raw)
The following changes since commit ff90d0e91aec252d3f5986df9ce02293cddadbca:
build-appliance-image: Update to dunfell head revision (2022-03-14 14:45:29 +0000)
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):
mobile-broadband-provider-info: upgrade 20201225 -> 20210805
Changhyeok Bae (1):
mobile-broadband-provider-info: upgrade 20210805 -> 20220315
Davide Gardenal (2):
re2c: backport fix for CVE-2018-21232
qemu: backport fix for CVE-2020-13253
Minjae Kim (1):
bluez5: fix CVE-2021-3658
Ovidiu Panait (1):
openssl: upgrade 1.1.1l -> 1.1.1n
Ralph Siemsen (2):
libxml2: backport fix for CVE-2022-23308
libxml2: move to gitlab.gnome.org
Richard Purdie (3):
python3targetconfig: Use for nativesdk too
oeqa/runtime/ping: Improve failure message to include more detail
oeqa/selftest/tinfoil: Improve tinfoil event test debugging
Tim Orling (1):
python3: upgrade 3.8.12 -> 3.8.13
wangmy (1):
linux-firmware: upgrade 20220209 -> 20220310
meta/classes/python3targetconfig.bbclass | 12 +
meta/lib/oeqa/runtime/cases/ping.py | 20 +-
meta/lib/oeqa/selftest/cases/tinfoil.py | 4 +-
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
.../bluez5/bluez5/CVE-2021-3658.patch | 95 +++++
.../mobile-broadband-provider-info_git.bb | 7 +-
.../openssl/openssl/CVE-2021-4160.patch | 145 --------
.../{openssl_1.1.1l.bb => openssl_1.1.1n.bb} | 4 +-
.../libxml/libxml2/CVE-2022-23308.patch | 204 ++++++++++
meta/recipes-core/libxml/libxml2_2.9.10.bb | 11 +-
...-detection-of-mips-architecture-for-.patch | 42 ++-
.../{python3_3.8.12.bb => python3_3.8.13.bb} | 6 +-
meta/recipes-devtools/qemu/qemu.inc | 5 +
.../qemu/qemu/CVE-2020-13253_1.patch | 50 +++
.../qemu/qemu/CVE-2020-13253_2.patch | 112 ++++++
.../qemu/qemu/CVE-2020-13253_3.patch | 86 +++++
.../qemu/qemu/CVE-2020-13253_4.patch | 139 +++++++
.../qemu/qemu/CVE-2020-13253_5.patch | 54 +++
...20220209.bb => linux-firmware_20220310.bb} | 6 +-
.../re2c/re2c/CVE-2018-21232-1.patch | 347 ++++++++++++++++++
.../re2c/re2c/CVE-2018-21232-2.patch | 243 ++++++++++++
.../re2c/re2c/CVE-2018-21232-3.patch | 156 ++++++++
.../re2c/re2c/CVE-2018-21232-4.patch | 166 +++++++++
meta/recipes-support/re2c/re2c_1.0.1.bb | 6 +-
24 files changed, 1730 insertions(+), 191 deletions(-)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2021-3658.patch
delete mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2021-4160.patch
rename meta/recipes-connectivity/openssl/{openssl_1.1.1l.bb => openssl_1.1.1n.bb} (97%)
create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-23308.patch
rename meta/recipes-devtools/python/{python3_3.8.12.bb => python3_3.8.13.bb} (98%)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13253_1.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13253_2.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13253_3.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13253_4.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13253_5.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20220209.bb => linux-firmware_20220310.bb} (99%)
create mode 100644 meta/recipes-support/re2c/re2c/CVE-2018-21232-1.patch
create mode 100644 meta/recipes-support/re2c/re2c/CVE-2018-21232-2.patch
create mode 100644 meta/recipes-support/re2c/re2c/CVE-2018-21232-3.patch
create mode 100644 meta/recipes-support/re2c/re2c/CVE-2018-21232-4.patch
--
2.25.1
next reply other threads:[~2022-03-23 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 22:28 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 2:32 [OE-core][dunfell 00/13] Pull request (cover letter only) 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.1648074246.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox