From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Clement Ramirez <ramirez.clement3@gmail.com>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Olivier Schonken <olivier.schonken@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/cups: security bump version to 2.4.6
Date: Mon, 21 Aug 2023 15:40:18 +0200 [thread overview]
Message-ID: <20230821154018.6a19f474@windsurf> (raw)
In-Reply-To: <20230817125236.985073-1-ramirez.clement3@gmail.com>
Hello Clément!
On Thu, 17 Aug 2023 14:52:36 +0200
Clement Ramirez <ramirez.clement3@gmail.com> wrote:
> Fixes CVE-2023-34241 (see [0] for details)
>
> [0] https://github.com/OpenPrinting/cups/releases/tag/v2.4.6
>
> Signed-off-by: Clement Ramirez <ramirez.clement3@gmail.com>
> ---
> package/cups/cups.hash | 2 +-
> package/cups/cups.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master after extending the commit log to explain that
bumping from 2.4.4 to 2.4.6 is OK as there are very few changes (and
adding the list of commits). Indeed if there had been too many changes,
a backport of the security fix could have been preferable. But here, a
bump is fine.
Thanks a lot for this contribution!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-21 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 12:52 [Buildroot] [PATCH 1/1] package/cups: security bump version to 2.4.6 Clement Ramirez
2023-08-21 13:40 ` Thomas Petazzoni via buildroot [this message]
2023-09-13 7:42 ` 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=20230821154018.6a19f474@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=olivier.schonken@gmail.com \
--cc=ramirez.clement3@gmail.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox