From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/8] Patch review
Date: Sun, 6 Nov 2022 06:03:45 -1000 [thread overview]
Message-ID: <cover.1667750511.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell and have comments back by
end of day Tuesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4435
The following changes since commit 54bbfe94ae4514386c572564bf221edfdbb2ce38:
selftest: skip virgl test on all Alma Linux (2022-10-21 06:28:52 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Alexander Kanavin (1):
tzdata: update to 2022d
Bartosz Golaszewski (1):
bluez5: add dbus to RDEPENDS
Daniel McGregor (1):
coreutils: add openssl PACKAGECONFIG
Frank de Brabander (1):
cve-update-db-native: add timeout to urlopen() calls
Hitendra Prajapati (2):
golang: CVE-2022-2880 ReverseProxy should not forward unparseable
query parameters
libX11: CVE-2022-3554 Fix memory leak
Ranjitsinh Rathod (1):
expat: Fix CVE-2022-43680 for expat
Teoh Jay Shen (1):
vim: Upgrade 9.0.0598 -> 9.0.0614
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
meta/recipes-core/coreutils/coreutils_8.31.bb | 1 +
.../expat/expat/CVE-2022-43680.patch | 33 ++++
meta/recipes-core/expat/expat_2.2.9.bb | 1 +
.../recipes-core/meta/cve-update-db-native.bb | 9 +-
meta/recipes-devtools/go/go-1.14.inc | 1 +
.../go/go-1.14/CVE-2022-2880.patch | 164 ++++++++++++++++++
meta/recipes-extended/timezone/timezone.inc | 6 +-
.../xorg-lib/libx11/CVE-2022-3554.patch | 58 +++++++
.../recipes-graphics/xorg-lib/libx11_1.6.9.bb | 1 +
meta/recipes-support/vim/vim.inc | 4 +-
11 files changed, 272 insertions(+), 7 deletions(-)
create mode 100644 meta/recipes-core/expat/expat/CVE-2022-43680.patch
create mode 100644 meta/recipes-devtools/go/go-1.14/CVE-2022-2880.patch
create mode 100644 meta/recipes-graphics/xorg-lib/libx11/CVE-2022-3554.patch
--
2.25.1
next reply other threads:[~2022-11-06 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 16:03 Steve Sakoman [this message]
2022-11-06 16:03 ` [OE-core][dunfell 1/8] golang: CVE-2022-2880 ReverseProxy should not forward unparseable query parameters Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 2/8] libX11: CVE-2022-3554 Fix memory leak Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 3/8] expat: Fix CVE-2022-43680 for expat Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 4/8] cve-update-db-native: add timeout to urlopen() calls Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 5/8] vim: Upgrade 9.0.0598 -> 9.0.0614 Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 6/8] tzdata: update to 2022d Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 7/8] coreutils: add openssl PACKAGECONFIG Steve Sakoman
2022-11-06 16:03 ` [OE-core][dunfell 8/8] bluez5: add dbus to RDEPENDS Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 14:20 [OE-core][dunfell 0/8] Patch review Steve Sakoman
2023-01-11 14:34 Steve Sakoman
2022-04-04 2:30 Steve Sakoman
2020-12-28 14:35 Steve Sakoman
2020-10-15 14:15 Steve Sakoman
2020-06-02 0:12 Steve Sakoman
2020-05-11 14:38 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.1667750511.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