From: Peter Korsgaard <peter@korsgaard.com>
To: Robert Smigielski <ptdropper@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] CycloneDX SBOM support
Date: Tue, 29 Aug 2023 15:10:47 +0200 [thread overview]
Message-ID: <878r9u56zs.fsf@48ers.dk> (raw)
In-Reply-To: <CABWt4etN4AfouYoaLc_-VgO=qU8F_o_ZU6RgMye8BzcB4w28Gg@mail.gmail.com> (Robert Smigielski's message of "Mon, 28 Aug 2023 19:19:08 -0400")
>>>>> "Robert" == Robert Smigielski <ptdropper@gmail.com> writes:
Hi,
> Yes I am concerned with creating a valid CycloneDX official SBOM for use in
> other projects as an input. For example take the output file
> <product>.json as input to Dependency Track. It does work. That is exactly
> what I need for my daily work.
And a generally useful thing!
> If data is not in the legal-info, then no problem, the CycloneDX-Buildroot
> project will not see it.
Longer term I think that is a problem (which you now also see with the
missing CPE identifiers). The legal-info format is very simple/old, so it
misses a number of things present in show-info that could be interesting
for a SBOM.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-29 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 12:55 [Buildroot] CycloneDX SBOM support Robert Smigielski
2023-08-28 6:00 ` Peter Korsgaard
2023-08-28 11:38 ` Michael Nosthoff via buildroot
2023-08-28 12:11 ` Robert Smigielski
2023-08-28 14:57 ` Peter Korsgaard
2023-08-28 19:38 ` Arnout Vandecappelle via buildroot
2023-08-28 19:57 ` Peter Korsgaard
2023-08-28 23:19 ` Robert Smigielski
2023-08-29 6:55 ` Arnout Vandecappelle via buildroot
2023-08-29 13:10 ` Peter Korsgaard [this message]
2023-08-29 13:38 ` Robert Smigielski
2023-09-13 15:12 ` Robert Smigielski
2023-08-28 23:12 ` Robert Smigielski
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=878r9u56zs.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ptdropper@gmail.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.