From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/libcurl: ignore CVE-2024-32928
Date: Wed, 23 Oct 2024 22:32:06 +0200 [thread overview]
Message-ID: <20241023223206.27f7e378@windsurf> (raw)
In-Reply-To: <462871d252e473dfd0850058abdffb85c5c90f79.1729511657.git.baruch@tkos.co.il>
On Mon, 21 Oct 2024 14:54:17 +0300
Baruch Siach via buildroot <buildroot@buildroot.org> wrote:
> This vulnerability only affects libcurl deployments in Nest products
> because of incorrect use.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/libcurl/libcurl.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks.
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:[~2024-10-23 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 11:54 [Buildroot] [PATCH] package/libcurl: ignore CVE-2024-32928 Baruch Siach via buildroot
2024-10-23 20:32 ` Thomas Petazzoni via buildroot [this message]
2024-11-09 16: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=20241023223206.27f7e378@windsurf \
--to=buildroot@buildroot.org \
--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