Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

How cve-check-tool resolve custom package name assigned to a package in a recipe? #59

Open
NaeemKK opened this issue Mar 10, 2017 · 0 comments
Open

How cve-check-tool resolve custom package name assigned to a package in a recipe? #59

NaeemKK opened this issue Mar 10, 2017 · 0 comments

Comments

@NaeemKK
Copy link

NaeemKK commented Mar 10, 2017

I am confused and unable to determine how cve-check-tool resolve the custom package name while finding CVE e.g. I have assigned my own name to the kernel i.e. "Linux-naeem" but using upstream version number.Now how does this tool find CVE by just looking at the name that is not any name of upstream package against which CVE are reported in NVD.
@NaeemKK NaeemKK changed the title How cve-check-tool resolve custom name assigned to a package in a recipe? How cve-check-tool resolve custom package name assigned to a package in a recipe? Mar 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NaeemKK