Migrate Alpine importer to advisory V2#2111
Migrate Alpine importer to advisory V2#2111ziadhany wants to merge 7 commits intoaboutcode-org:mainfrom
Conversation
|
|
@TG1999 @pombredanne I have a question about Alpine migration. We are fetching one URL and processing the data without grouping by CVE. The problem is that each URL reports a package version along with its fixed CVEs. How can we obtain a unique identifier for this importer? Is it a good idea to restructure the data and create a large mapping, using the CVE as the unique identifier? Proposed structure: Example: Sources: |
| ) | ||
|
|
||
| for cve in aliases: | ||
| advisory_id = f"{pkg_infos['name']}/{qualifiers['distroversion']}/{cve}" |
There was a problem hiding this comment.
ex:
apache2/v3.20/2.4.26-r0/CVE-2017-7668
vulnerabilities/tests/pipelines/v2_importers/test_alpine_linux_importer_pipeline.py
Show resolved
Hide resolved
|
The logs in debug mode: |
keshav-space
left a comment
There was a problem hiding this comment.
Thanks @ziadhany, see comments below.
vulnerabilities/pipelines/v2_importers/alpine_linux_importer.py
Outdated
Show resolved
Hide resolved
vulnerabilities/pipelines/v2_importers/alpine_linux_importer.py
Outdated
Show resolved
Hide resolved
Signed-off-by: ziad hany <ziadhany2016@gmail.com>
…aseImporterPipelineV2 Signed-off-by: ziad hany <ziadhany2016@gmail.com>
Signed-off-by: ziad hany <ziadhany2016@gmail.com>
Fix duplication on advisory_id Signed-off-by: ziad hany <ziadhany2016@gmail.com>
Signed-off-by: ziad hany <ziadhany2016@gmail.com>
26f912d to
0bb7b03
Compare
Signed-off-by: ziad hany <ziadhany2016@gmail.com>
Issue: