From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 1/2] package/luajit: add CPE_VERSION & CPE_UPDATE
Date: Mon, 11 Aug 2025 12:01:58 +0200 [thread overview]
Message-ID: <877bzanpm1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250807152907.3225581-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Thu, 7 Aug 2025 17:29:06 +0200")
>>>>> "Thomas" == Thomas Perale via buildroot <buildroot@buildroot.org> writes:
> Since this package hasn't had a proper release in a while this patch set
> the CPE_VERSION and CPE_UPDATE to the latest tags available.
> The annotation available on NVD all refers to this last available
> version `cpe:2.3:a:luajit:luajit:2.1.0:beta3:*:*:*:*:*:*`.
> See https://nvd.nist.gov/vuln/detail/CVE-2020-15890 for instance.
> 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
next prev parent reply other threads:[~2025-08-11 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 15:29 [Buildroot] [PATCH 1/2] package/luajit: add CPE_VERSION & CPE_UPDATE Thomas Perale via buildroot
2025-08-07 15:29 ` [Buildroot] [PATCH 2/2] package/luajit: ignore multiple CVEs Thomas Perale via buildroot
2025-08-11 10:02 ` Peter Korsgaard
2025-08-21 19:20 ` Thomas Perale via buildroot
2025-08-11 10:01 ` Peter Korsgaard [this message]
2025-08-21 19:20 ` [Buildroot] [PATCH 1/2] package/luajit: add CPE_VERSION & CPE_UPDATE 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=877bzanpm1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.perale@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 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.