| Summary: | Implement CPE to package to Release mapping | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Security Response Tool | Reporter: | David Reyna <david.reyna> |
| Component: | General | Assignee: | David Reyna <david.reyna> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | randy.macleod, ross.burton |
| Version: | 2.7 | ||
| Target Milestone: | 5.0 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | NIR 11/03 | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
David Reyna
2018-12-29 09:36:49 UTC
We have been working on an implementation, and it will be ready for YP-3.3 It turns out that this is very very hard, give the poor mapping of CPEs to recipes, even when CPEs are avialable. My new strategy is to find ways to integrate with existing second and third tools in an agnostic manner. Perhaps data from CVE Checker can help provide advice on how to proceed. Wind River's solution is that our triage management identifies the recipe from the CVE (mostly form the description given that the CPE table is usually empty for new CVEs), and our defect system tracks the CVEs by those recipe names. Ideally we have at least semi-automated assistance in those mappings. David I am moving this away from "NEEDINFO". While this feature request definity needs more information about systemic difficulties in finding a resolution, it does not need the urgency of NEEDINFO. This needs a mandate to implement. Will re-file new defect when that happens. |