Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>,
	 Daniel Price <daniel.price@gmail.com>,
	 Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	 Danomi Manchego <danomimanchego123@gmail.com>,
	 Titouan Christophe <titouan.christophe@mind.be>,
	 Olivier Schonken <olivier.schonken@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/libgit2: update CPE vendor
Date: Sat, 30 May 2026 11:00:42 +0200	[thread overview]
Message-ID: <8733z98e6d.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260529094514.178266-6-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Fri, 29 May 2026 11:45:13 +0200")

>>>>> "Thomas" == Thomas Perale via buildroot <buildroot@buildroot.org> writes:

 > The CPE "cpe:2.3:a:libgit2:libgit2:*:*:*:*:*:*:*:*" is valid for this
 > package.

 > The previous CPE hasn't been used since 2016 while the new one has 10
 > new CVEs assigned to it.

 > See the GHSA [1] and the associated CVE [2].

 > [1] https://github.com/libgit2/libgit2/security/advisories/GHSA-j2v7-4f6v-gpg8
 > [2] https://nvd.nist.gov/vuln/detail/cve-2024-24577

 > Signed-off-by: Thomas Perale <thomas.perale@mind.be>

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-05-30  9:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  9:45 [Buildroot] [PATCH] pacakge/jq: update CPE vendor Thomas Perale via buildroot
2026-05-29  9:45 ` [Buildroot] [PATCH] package/hiredis: " Thomas Perale via buildroot
2026-05-30  8:54   ` Peter Korsgaard
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-05-29  9:45 ` [Buildroot] [PATCH] package/redis: " Thomas Perale via buildroot
2026-05-30  8:56   ` Peter Korsgaard
2026-05-30 10:10     ` Titouan Christophe via buildroot
2026-06-05 12:51   ` Thomas Perale via buildroot
2026-05-29  9:45 ` [Buildroot] [PATCH] package/cups-filter: " Thomas Perale via buildroot
2026-05-30  8:59   ` Peter Korsgaard
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-05-29  9:45 ` [Buildroot] [PATCH] package/icu: " Thomas Perale via buildroot
2026-05-30  9:02   ` Peter Korsgaard
2026-06-05 12:51   ` Thomas Perale via buildroot
2026-05-29  9:45 ` [Buildroot] [PATCH] package/libgit2: " Thomas Perale via buildroot
2026-05-30  9:00   ` Peter Korsgaard [this message]
2026-06-05 12:51   ` Thomas Perale via buildroot
2026-05-29  9:45 ` [Buildroot] [PATCH] package/gstreamer1: " Thomas Perale via buildroot
2026-05-30  9:03   ` Peter Korsgaard
2026-06-05 12:50   ` Thomas Perale via buildroot
2026-05-30  8:53 ` [Buildroot] [PATCH] pacakge/jq: " Peter Korsgaard
2026-06-05 12:50 ` 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=8733z98e6d.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=danomimanchego123@gmail.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=olivier.schonken@gmail.com \
    --cc=thomas.perale@mind.be \
    --cc=titouan.christophe@mind.be \
    /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