From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/zchunk: security bump to version 1.3.2
Date: Mon, 30 Oct 2023 18:22:45 +0100 [thread overview]
Message-ID: <87y1fk2ffe.fsf@48ers.dk> (raw)
In-Reply-To: <20231028153448.142511-2-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 28 Oct 2023 17:34:48 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Drop patches (already in version)
> - tests can be disabled since version 1.2.3 and
> https://github.com/zchunk/zchunk/commit/e2e3d6b14e944530837db43dd73413ce84a1e1f5
> - docs can be disabled since version 1.2.3 and
> https://github.com/zchunk/zchunk/commit/af6c10e8be324d1194982c6a8db001f72d50dbf6
> - Fix CVE-2023-46228: zchunk before 1.3.2 has multiple integer overflows
> via malformed zchunk files to lib/comp/comp.c, lib/comp/zstd/zstd.c,
> lib/dl/multipart.c, or lib/header.c.
> https://github.com/zchunk/zchunk/compare/1.2.2...1.3.2
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-30 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 15:34 [Buildroot] [PATCH 1/2] package/zchunk: add ZCHUNK_CPE_ID_VENDOR Fabrice Fontaine
2023-10-28 15:34 ` [Buildroot] [PATCH 2/2] package/zchunk: security bump to version 1.3.2 Fabrice Fontaine
2023-10-30 17:22 ` Peter Korsgaard [this message]
2023-10-28 21:03 ` [Buildroot] [PATCH 1/2] package/zchunk: add ZCHUNK_CPE_ID_VENDOR Yann E. MORIN
2023-10-30 17:22 ` Peter Korsgaard
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=87y1fk2ffe.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=james.hilliard1@gmail.com \
/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.