From: "Sven Püschel" <s.pueschel@pengutronix.de>
To: ptxdist@pengutronix.de, Martin Domig <martin.domig@wolfvision.net>
Subject: Re: [ptxdist] [PATCH] libxml2: set CVE_PRODUCT
Date: Fri, 20 Nov 2026 18:40:10 +0100 [thread overview]
Message-ID: <7a0c07ef-4d85-4937-9e22-cc42a96e2ca9@pengutronix.de> (raw)
In-Reply-To: <20261120-apache-devotee-c70ae6ce21bf@thorsis.com>
Hi Alexander,
On 11/20/26 17:43, Alexander Dahl wrote:
> Hello,
>
> Am Fri, Nov 20, 2026 at 05:29:37PM +0100 schrieb Sven Püschel:
>> From: Martin Domig <martin.domig@wolfvision.net>
> It would be nice to see some reasoning here. Why is this necessary?
> The currently used cpe:2.3:a:*:libxml2:*:*:*:*:*:*:*:* matches the
> library just fine:
> https://nvd.nist.gov/products/cpe/search/results?keyword=cpe:2.3:a:*:libxml2:*:*:*:*:*:*:*:*
>> Signed-off-by: Martin Domig <martin.domig@wolfvision.net>
>> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
>> ---
>> rules/libxml2.make | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/rules/libxml2.make b/rules/libxml2.make
>> index a2b20b03b..5c6451bba 100644
>> --- a/rules/libxml2.make
>> +++ b/rules/libxml2.make
>> @@ -30,6 +30,7 @@ LIBXML2_LICENSE_FILES := \
>>
>> LIBXML2_URL := \
>> $(call ptx/mirror, GNOME, libxml2/$(basename $(LIBXML2_VERSION))/$(LIBXML2).$(LIBXML2_SUFFIX))
>> +LIBXML_CVE_PRODUCT := xmlsoft:libxml2
> This should probably be LIBXML2_CVE_PRODUCT. Did you actually test
> this?
sorry and thanks for the catch. For the patches I've just did a quick
check that the CVE product name looked correct. They just looked too
trivial...
Sincerely
Sven
>
> Greets
> Alex
>
>>
>> # ----------------------------------------------------------------------------
>> # Prepare
>> --
>> 2.47.3
>>
>>
prev parent reply other threads:[~2026-11-20 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 16:29 Sven Püschel
2026-11-20 16:43 ` Alexander Dahl via ptxdist
2026-11-20 17:40 ` Sven Püschel [this message]
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=7a0c07ef-4d85-4937-9e22-cc42a96e2ca9@pengutronix.de \
--to=s.pueschel@pengutronix.de \
--cc=martin.domig@wolfvision.net \
--cc=ptxdist@pengutronix.de \
/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