Bug 11183

Summary: Evaluate "native" CVE scanning solution
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Joshua Lock <joshuagloe>
Component: coreAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: clopez, meta.mr.watcher, meta.watcher, randy.macleod, sona.sarmadi, yue.tao
Version: 2.4   
Target Milestone: 4.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Joshua Lock 2017-03-17 15:35:42 UTC
We've run into several issues trying to integrate cve-check-tool into the YP workflow and the upstream is less active than we'd like.

We could write our own Python tool to integrate more cleanly with YP. Instead of harvesting the full CVE database we could simplify both the tool and the work it generates by scraping LWN's curated weekly CVE list?
Comment 1 Carlos Alberto Lopez Perez 2017-08-15 20:56:04 UTC
Is this maybe a duplicated of bug 10722 ?
Comment 2 Carlos Alberto Lopez Perez 2017-08-15 20:56:51 UTC
(In reply to comment #1)
> Is this maybe a duplicated of bug 10722 ?

Sorry, I mean bug 10772
Comment 3 Robin Jordan 2018-02-26 20:36:46 UTC
Please provide a status on this?  Is it a duplicate?  If not, will it be ready for YP 2.5 M3?
Comment 4 Ross Burton 2018-02-26 23:18:22 UTC
No, punted to 2.6 already.
Comment 5 Ross Burton 2018-06-28 09:40:21 UTC
*** Bug 10771 has been marked as a duplicate of this bug. ***
Comment 6 Ross Burton 2019-07-25 15:03:46 UTC
As of oe-core 5388ed6d1378d647a65912dbd537f9ef3cb5760a cve-check-tool has been removed and cve-check.bbclass does the work itself.