WIP: Feature indicated namespace #678
Closed
Conversation
This file contains 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
The table is to track raw potential contextual information about a Feature. It's useful for helping Clair to determine the namespace of a feature.
KeyboardNerd
changed the title
|
closed |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The table is to track raw potential contextual information about a
Feature. It's useful for helping Clair to determine the namespace of a
feature.
Work in progress, the raw contextual data will be stored in the database, and interpreted by the Clair logic to relate the feature with some namespace in the layer or not.
This will result in better scanning result for multiple namespaces feature by reducing the number of wrong namespaces of feature.
For example:
CentOS:7 may install a RHEL package, which is compatible, using RPM. Since the package is compiled for the RHEL system, it should be considered a package with RHEL namespace, and affected by RHEL vulnerabilities.
We can extract this information by looking at the version string: e.g. curl-7.29.0-51.el7.x86_64
From the version string, we can understand that it's packaged for RHEL7 X86_64 (el7). We store this information in the database, so that the namespace can be determined correctly.