Skip to content

SBOM generation tool fails during gitignore filtering for libraries with no files #122044

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sethmlarson opened this issue Jul 19, 2024 · 5 comments
Assignees
Labels
type-security A security issue

Comments

@sethmlarson
Copy link
Contributor

sethmlarson commented Jul 19, 2024

Within #119316 the libb2 library was removed. When running the SBOM generation tool a confusing error is raised during gitignore filtering instead of triggering the helpful error for the "no files for package" condition. This can be avoided by short-circuiting gitignore filtering when no files are present.

Linked PRs

@ZeroIntensity
Copy link
Member

Looks like this is not a security issue, just a bug.

@Eclips4
Copy link
Member

Eclips4 commented Jul 20, 2024

Looks like this is not a security issue, just a bug.

I guess that all of the SBOM-related issues are actually related to type-security label.

@sethmlarson
Copy link
Contributor Author

We can change the labeling scheme if it makes it less confusing! :)

@ZeroIntensity
Copy link
Member

I was under the impression that type-security was reserved for things that actually posed a security thread, not things related to packages for cryptography and whatnot.

@hugovk
Copy link
Member

hugovk commented Jul 27, 2024

Merged and backported, thanks!

@hugovk hugovk closed this as completed Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-security A security issue
Projects
None yet
Development

No branches or pull requests

4 participants