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?
Is this maybe a duplicated of bug 10722 ?
(In reply to comment #1) > Is this maybe a duplicated of bug 10722 ? Sorry, I mean bug 10772
Please provide a status on this? Is it a duplicate? If not, will it be ready for YP 2.5 M3?
No, punted to 2.6 already.
*** Bug 10771 has been marked as a duplicate of this bug. ***
As of oe-core 5388ed6d1378d647a65912dbd537f9ef3cb5760a cve-check-tool has been removed and cve-check.bbclass does the work itself.