From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/4] package/unzip: import patches from Debian
Date: Fri, 29 May 2026 11:45:54 +0200 [thread overview]
Message-ID: <ahlfm8PQMCidZ3TT@windsurf> (raw)
In-Reply-To: <20260204131841.282589-1-thomas.perale@mind.be>
Hello Thomas,
On Wed, Feb 04, 2026 at 02:18:30PM +0100, Thomas Perale via buildroot wrote:
> In Buildroot there are multiple way to apply patches on a package [1]
>
> - Adding `.patch` file in the package directory.
> - Define `<pkg>_PATCH` variable with the location of the patch tar.gz.
> It used to download Debian patches tarball.
> - Implement custom patching logic with `PRE`/`POST` patches hooks.
>
> To make the CycloneDX SBOM generation not dependant on downloading the
> packages, the two last options have the downside of not appearing on the
> generated SBOM.
>
> The unzip package is downloading a tarball from the Debian mirror with
> the `<pkg>_PATCH` method [2].
>
> To improve the tracking of the patched vulnerabilities for the unzip
> package this commit import the patches previously downloaded with the
> `_PATCH` variable in the Buildroot tree.
> This allows to add the `CVE:` trailer [3] on the patches that fix
> vulnerabilities to better track which patch is fixing the vulnerability.
>
> [1] https://buildroot.org/downloads/manual/manual.html#patch-policy
> [2] https://snapshot.debian.org/archive/debian/20250311T215724Z/pool/main/u/unzip/unzip_6.0-29.debian.tar.xz
> [3] 1167d0ff3d docs/manual: mention CVE trailer
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Thanks a lot, entire series applied to master.
Actually PATCH 3/4 is fixing a pretty nasty bug: we were pretending
that some of the CVEs were fixed by patches, but we were not actually
applying those patches, so the CVEs were not actually fixed.
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:[~2026-05-29 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 13:18 [Buildroot] [PATCH 1/4] package/unzip: import patches from Debian Thomas Perale via buildroot
2026-02-04 13:18 ` [Buildroot] [PATCH 2/4] package/heirloom-mailx: " Thomas Perale via buildroot
2026-06-05 12:49 ` Thomas Perale via buildroot
2026-02-04 13:18 ` [Buildroot] [PATCH 3/4] package/libmad: remove Debian patches Thomas Perale via buildroot
2026-06-05 12:49 ` Thomas Perale via buildroot
2026-02-04 13:18 ` [Buildroot] [PATCH 4/4] package/libmad: add patch for CVE-2017-837{2, 3, 4} Thomas Perale via buildroot
2026-06-05 12:49 ` Thomas Perale via buildroot
2026-05-29 9:45 ` Thomas Petazzoni via buildroot [this message]
2026-06-05 12:49 ` [Buildroot] [PATCH 1/4] package/unzip: import patches from Debian Thomas Perale 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=ahlfm8PQMCidZ3TT@windsurf \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.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 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.