Confirmation about report results display in image detail page #196
-
|
Hi Fabrizio, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Answers from Flavio from Slack
This is correct. It's however important for you to understand why this is happening, and how to handle that. However it's important that the user knows that /bin/foo is affected by a CVE because it's using an outdated version of the go compiler. The entry in the table should be about /bin/foo, not the go compiler. |
Beta Was this translation helpful? Give feedback.
-
|
@xingzhang-suse: please consider creating 1 discussion per topic. |
Beta Was this translation helpful? Give feedback.
-
|
@flavio Sure, I have split the discussion |
Beta Was this translation helpful? Give feedback.
-
|
@xingzhang-suse if this is resolved, let's mark the answer as accepted, see https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion#marking-a-comment-as-an-answer |
Beta Was this translation helpful? Give feedback.
Answers from Flavio from Slack
https://suse.slack.com/archives/C08GX5XJ996/p1759907629206429?thread_ts=1759900625.194909&cid=C08GX5XJ996
This is correct. It's however important for you to understand why this is happening, and how to handle that.
A report might include results about system packages and also binaries that have not been installed via the package manager.
Everything has to be put into the same table.
However it's important that the user knows that /bin/foo is affected by a CVE because it's using an outdated version of the go compiler. The entry in the table should be about /bin/foo, not the go compiler.
Of course that me…