Skip to content
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

Add package_kind to vulnerability query #209

Merged
merged 1 commit into from
Aug 19, 2020

Conversation

Allda
Copy link
Collaborator

@Allda Allda commented Aug 4, 2020

By adding package kind to database vulnerability query we query only
real affected packages. Without this code Clair produce false negatives
in case source package and binary package has same name.

When vulnerability is issued with source package all binary package that
have come from same source are marked as vulnerable.

@Allda
Copy link
Collaborator Author

Allda commented Aug 7, 2020

@ldelossa I change a query to doesn't require package kind if it is not defined in vulnerability. This way updaters that support package kinds have more precise matching results and updaters that doesn't support it yet are not affected by this change.

@Allda Allda force-pushed the package_kind_query branch 2 times, most recently from 23eecb9 to e20862e Compare August 12, 2020 14:15
By adding package kind to database vulnerability query we query only
real affected packages. Without this code Clair produce false negatives
in case source package and binary package has same name.

When vulnerability is issued with source package all binary package that
have come from same source are marked as vulnerable.
@ldelossa ldelossa merged commit c5d0f27 into quay:master Aug 19, 2020
ldelossa pushed a commit that referenced this pull request Aug 23, 2020
By adding package kind to database vulnerability query we query only
real affected packages. Without this code Clair produce false negatives
in case source package and binary package has same name.

When vulnerability is issued with source package all binary package that
have come from same source are marked as vulnerable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants