From: "hongxu" <hongxu.jia@eng.windriver.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][scarthgap][PATCH 1/4] Use 7zip 24.09 to replace p7zip 16.02
Date: Sun, 22 Dec 2024 00:29:59 -0800 [thread overview]
Message-ID: <14778.1734856199190674571@lists.openembedded.org> (raw)
In-Reply-To: <20241222081612.239474-1-hongxu.jia@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
Hi Armin,
The p7zip is too old and dead since 2016 and has many vulnerable CVEs, such as:
CVE-2024-11612
CVE-2024-11477
CVE-2023-52169
CVE-2023-52168
CVE-2023-40481
CVE-2023-31102
CVE-2023-1576
CVE-2022-47069
The 7z is a standalone command, and the version of all affected recipes (android-tools, python3-rarfile, xarchiver) has no change between master and scarthgap
so I back ported the new 7zip recipe to scarthgap to instead of p7zip, I think the regression is little
//Hongxu
[-- Attachment #2: Type: text/html, Size: 684 bytes --]
next prev parent reply other threads:[~2024-12-22 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 8:16 [meta-oe][scarthgap][PATCH 1/4] Use 7zip 24.09 to replace p7zip 16.02 Hongxu Jia
2024-12-22 8:16 ` [meta-oe][scarthgap][PATCH 2/4] Update p7zip to 7zip Hongxu Jia
2024-12-22 8:16 ` [meta-oe][scarthgap][PATCH 3/4] android-tools: fix warning: library search path "/usr/lib/p7zip" is unsafe for cross-compilation Hongxu Jia
2024-12-22 8:16 ` [meta-oe][scarthgap][PATCH 4/4] 7zip: Fix build with clang Hongxu Jia
2024-12-22 8:29 ` hongxu [this message]
2024-12-23 16:03 ` [oe] [meta-oe][scarthgap][PATCH 1/4] Use 7zip 24.09 to replace p7zip 16.02 Marko, Peter
2024-12-25 5:16 ` Martin Jansa
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=14778.1734856199190674571@lists.openembedded.org \
--to=hongxu.jia@eng.windriver.com \
--cc=openembedded-devel@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.