Package CVE Reporting
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest9 of 26 patches 0 repliesNew
9 of 26 patches are in this archive. The cover letter announces 26.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/26 | cpe-info: new make target | +0 | 2 replies | |
| 2/26 | cpe-info: update manual for new pkg vars | +0 | 1 reply | |
| 3/26 | cpe-info: id prefix/suffix | +0 | 3 replies | |
| 4/26 | cpe-info: only report target pkgs | +0 | 1 reply | |
| 6/26 | boa: add CPE id | +0 | 1 reply | |
| 6/26 | boa: add CPE id | +0 | 3 replies | |
| 6/26 | boa: add CPE id | +0 | 1 reply | |
| 20/26 | linux: add CPE id | +0 | 1 reply | |
| 20/26 | linux: add CPE id | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [NEXT 00/26] Package CVE Reporting
Hello,
Quoted 8 lines · Matt Weber
This series adds new infrastructure to report a packages CPE identifier in a similar way that the legal info is currently reported.
The addition of CPE IDs to the packages is a manual process, but in a later patchset additions are planned to the pkg-stats script to automate maintenance the process.
Thanks for working on this and coming up with a proposal!
While I'm fine with the package annotations, I am not yet sure that a "make cpe-info" is what we want here.
In particular, I'm thinking about the interaction with pkg-stats, and the work I've done to make pkg-stats query release-monitoring.org to check for new upstream versions. Ideally, pkg-stats should also query the CPE information and add it to its report.
For now, pkg-stats reports about all packages in Buildroot, but I'm hoping to improve that and make it possible for pkg-stats to only generate a report about the list of packages selected in the current Buildroot configuration.
So I don't have a very clear cut answer, but I see some overlap between cpe-info and pkg-stats, and I'd like to have a common view on what is the mid/long-term direction we want to take.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering http://bootlin.com