-
Notifications
You must be signed in to change notification settings - Fork 577
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
empty name #3194
Comments
I opened an pull request for it: |
@idefixcert thanks for the issue and the PR! We still have a couple questions before understanding the issue and reviewing the PR:
The code I think might need to be fixed is syft/syft/pkg/cataloger/kernel/parse_linux_kernel_module_file.go Lines 124 to 125 in fcd5ec9
Are you able to see what's going on there? Is it possible the kernel module specifies its name in a different field or something? |
I'm not sure if i'm in the exact same boat, but I was inspecting an SBOM for an image I built that was constructed with syft, and I have several instances of this for rubygems.
I can push the image somewhere public if it would be helpful to inspect, and/or share the full sbom. I notice in my case, each gem has the same (presumably) incomplete purl, so not 100% sure if this is the same issue as what opened this thread |
This might be addressed by #3257 when that is released. |
We believe this was fixed by #3257 release in Syft 1.14.0. If we're wrong, please let us know! |
What happened:
Some of the components I get on a system have an empty name like:
I looked into the code and saw that there is a IsValid function for packages (
syft/syft/pkg/package.go
Lines 83 to 85 in 1aaa644
but not all of the cataloger do respect that.
What you expected to happen:
I would expect that components (packages) that are not valid would not get exported.
Steps to reproduce the issue:
I ran that on a local filesystem.
Anything else we need to know?:
NO
Environment:
Output of
syft version
:latest master, because I also tested with the source and own compilation.
but also 1.11.1
OS (e.g:
cat /etc/os-release
or similar):in my case the following patch helped:
The text was updated successfully, but these errors were encountered: