From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: "Thomas Perale" <thomas.perale@mind.be>,
"Rémi Rérolle" <remi.rerolle@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/libfreeimage: various vulnerability patches
Date: Mon, 29 Dec 2025 17:51:31 +0100 [thread overview]
Message-ID: <20251229175131.4b44b95a@windsurf> (raw)
In-Reply-To: <20251013204005.42277-1-thomas.perale@mind.be>
On Mon, 13 Oct 2025 22:40:05 +0200
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:
> This package’s last release dates back to July 2018. Since then, a
> number of CVEs have accumulated. This patch applies several
> vulnerability fixes from the Fedora project. Not all vulnerabilities are
> addressed by this patch.
Thanks, I've applied. To be honest, an image parsing library with no
release since July 2018 seems crazy to me. The only reverse
dependencies in Buildroot are cegui (which nobody is updating) and ogre.
Should we drop all of this, and say no to unmaintained insecure
software?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-29 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 20:40 [Buildroot] [PATCH] package/libfreeimage: various vulnerability patches Thomas Perale via buildroot
2025-12-29 16:51 ` Thomas Petazzoni via buildroot [this message]
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot
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=20251229175131.4b44b95a@windsurf \
--to=buildroot@buildroot.org \
--cc=remi.rerolle@gmail.com \
--cc=thomas.perale@mind.be \
--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