From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/ipmitool: set IPMITOOL_CPE_ID_VALID
Date: Sun, 17 Jan 2021 17:19:47 +0100 [thread overview]
Message-ID: <20210117161947.GS2375@scaer> (raw)
In-Reply-To: <20210117143329.27231-1-heiko.thiery@gmail.com>
Heiko, All,
On 2021-01-17 15:33 +0100, Heiko Thiery spake thusly:
> cpe:2.3:a:ipmitool_project:ipmitool is a valid CPE identifier for this
> package:
>
> https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=ipmitool
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> ---
> package/ipmitool/ipmitool.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/ipmitool/ipmitool.mk b/package/ipmitool/ipmitool.mk
> index 123dd274f4..facd97a0b8 100644
> --- a/package/ipmitool/ipmitool.mk
> +++ b/package/ipmitool/ipmitool.mk
> @@ -9,6 +9,7 @@ IPMITOOL_SOURCE = ipmitool-$(IPMITOOL_VERSION).tar.bz2
> IPMITOOL_SITE = http://downloads.sourceforge.net/project/ipmitool/ipmitool/$(IPMITOOL_VERSION)
> IPMITOOL_LICENSE = BSD-3-Clause
> IPMITOOL_LICENSE_FILES = COPYING
> +IPMITOOL_CPE_ID_VENDOR = ipmitool_project
This is the default value when _CPE_ID_VALID is set to YES, so I
switched to that. Also, by the looksof the commit log, it looks like
that's what you indeed wanted to do, hopefully... ;-)
Applied to master, thanks.
Regards,
Yann E. MORIN.
> # 0008-fru-Fix-buffer-overflow-vulnerabilities.patch
> # 0009-fru-Fix-buffer-overflow-in-ipmi_spd_print_fru.patch
> --
> 2.20.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-01-17 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 14:33 [Buildroot] [PATCH] package/ipmitool: set IPMITOOL_CPE_ID_VALID Heiko Thiery
2021-01-17 14:33 ` [Buildroot] [PATCH] package/libyang: add LIBYANG_CPE_ID_VENDOR Heiko Thiery
2021-01-17 16:20 ` Yann E. MORIN
2021-01-17 16:19 ` Yann E. MORIN [this message]
2021-01-17 21:08 ` [Buildroot] [PATCH] package/ipmitool: set IPMITOOL_CPE_ID_VALID Heiko Thiery
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=20210117161947.GS2375@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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