From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] utils/generate-cyclonedx: fixup scp-style git sites
Date: Sun, 21 Jun 2026 12:36:49 +0200 [thread overview]
Message-ID: <87eci0b2ny.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260619090027.3145553-1-peter@korsgaard.com> (Peter Korsgaard's message of "Fri, 19 Jun 2026 11:00:26 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Commit e8c54ffb3d ("utils/generate-cyclonedx: generate vcs
> externalReferences for source repos") added externalReferences to the source
> code of packages.
> This unfortunately causes issues with packages (in br2-external) fetching
> from git using the scp-like syntax, E.G.:
> FOO_SITE_METHOD = git
> FOO_SITE = git@github.com:<project>/<repo>.git
> Which ends up in the SBOM as:
> [
> {
> "type": "vcs",
> "url": "git@github.com:<project>/<repo>.git",
> "comment": "git repository"
> }
> ]
> This (correctly) causes Dependency track to reject the SBOM import with:
> {
> "status": 400,
> "title": "The uploaded BOM is invalid",
> "detail": "Schema validation failed",
> "errors": [
> "$.components[2].externalReferences[0].url: does not match the iri-reference pattern must be a valid RFC 3987 IRI-reference",
> "$.components[2].externalReferences[0].url: does not match the iri-reference pattern must be a valid RFC 3987 IRI-reference",
> "$.components[2].externalReferences[0].url: does not match the regex pattern ^urn:cdx:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/[1-9][0-9]*$",
> ]
> }
> The CycloneDX spec indeed requires a URI:
> The URI (URL or URN) to the external reference. External references are
> URIs and therefore can accept any URL scheme including https (RFC-7230),
> mailto (RFC-2368), tel (RFC-3966), and dns (RFC-4501)
> https://cyclonedx.org/docs/1.6/json/#metadata_tools_oneOf_i0_components_items_externalReferences_items_url
> The user@host:project/repo.git is a git-specific shorthand for a git-over-ssh URL. From man git-clone:
> Git supports ssh, git, http, and https protocols (in addition, ftp and ftps
> can be used for fetching, but this is inefficient and deprecated; do not use
> them).
> The native transport (i.e. git:// URL) does no authentication and should
> be used with caution on unsecured networks.
> The following syntaxes may be used with them:
> • ssh://[user@]host.xz[:port]/path/to/repo.git/
> • git://host.xz[:port]/path/to/repo.git/
> • http[s]://host.xz[:port]/path/to/repo.git/
> • ftp[s]://host.xz[:port]/path/to/repo.git/
> An alternative scp-like syntax may also be used with the ssh protocol:
> • [user@]host.xz:path/to/repo.git/
> So convert the scp-like syntax to ssh:// URLs in parse_uris() for spec
> compliance.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-06-21 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 9:00 [Buildroot] [PATCH] utils/generate-cyclonedx: fixup scp-style git sites Peter Korsgaard
2026-06-20 9:39 ` Thomas Perale via buildroot
2026-06-21 10:36 ` Peter Korsgaard [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=87eci0b2ny.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox