Conversation
All packages should have the ability to list the affected files in them for a specific vulnerability to make it easier to programmatically filter out vulnerabilities for where the user does not even build the affected files into their image. Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Collaborator
|
I agree we definitely want to add this as a structured field. Though I think we need to have it in a more general field like what's proposed in #501 , as files probably doesn't apply as much when talking about language packages, where the boundary is more on either functions or modules. I'll add this to the next osv-schema meeting as a topic to discuss. |
Author
|
functions and modules were what I was going to propose next, they are all good things to have. I was just going to do one at at time, but can include them all as a patch series if you feel it would be acceptable that way. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All packages should have the ability to list the affected files in them for a specific vulnerability to make it easier to programmatically filter out vulnerabilities for where the user does not even build the affected files into their image.