| Summary: | Errors in CVE web pages | ||
|---|---|---|---|
| Product: | Websites | Reporter: | k s <kurt> |
| Component: | Other | Assignee: | Atelier Team <atelier-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | davidwhodgins |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
k s
2022-03-11 18:48:47 CET
Is there an actual need to correct this for Mageia versions the are EOL since several years? Also the pages can get opened, so no imminent problem at all. I tightened up the regex for ingesting the Mageia CVE data into the GlobalSecurityDatabase: https://github.com/kurtseifried/gsd-data-enrichment/blob/main/mageia/get-mageia-advisories.sh grep "<a href=\"CVE-[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9]*\.html\"" so for the GlobalSecurityDatabase we're good on the data ingestion, but I also believe "if you see a bug, at least report it" because otherwise, we end up with "why didn't you say something? we can fix that" =). So from my end I'm happy with WONTFIX EOL.
k s
2022-03-11 19:43:06 CET
Priority:
Normal =>
Low As per comments closing WONTFIX Resolution:
(none) =>
WONTFIX Fixed. Website will be updated the next time an update is released. I'm surprised you're parsing the html. It should be easier to parse the data used to generate the html. https://svnweb.mageia.org/advisories/ For any further advisory issues found, please assign the bug report directly to me. Thanks for reporting the issues. CC:
(none) =>
davidwhodgins |