| 2007-06-08 17:55:23 |
Kees Cook |
bug |
|
|
added bug |
| 2007-07-02 20:42:12 |
Diogo Matsubara |
malone: status |
New |
Incomplete |
|
| 2007-07-02 20:42:12 |
Diogo Matsubara |
malone: statusexplanation |
|
|
|
| 2007-07-04 15:13:26 |
Diogo Matsubara |
description |
When linking or displaying CVEs, Malone needs to make sure the name is correctly shown/parsed as CVE-YYYY-NNNN, so that search engines will be able to make sense of the links. The correct naming convention for CVEs is that they must start with "CVE". Currently, all the links show just YYYY-NNNN. |
When linking or displaying CVEs, Malone needs to make sure the name is correctly shown/parsed as CVE-YYYY-NNNN, so that search engines will be able to make sense of the links. The correct naming convention for CVEs is that they must start with "CVE". Currently, all the links show just YYYY-NNNN.
Other places that would be useful to use the convetion:
- "Link to CVE" page needs to take full CVE name, including "CVE-" prefix
- "CVE Reference" box for bugs that have linked CVEs
- CVE page needs missing dash between "CVE" and index number (e.g. lhttps://bugs.launchpad.net/bugs/cve/2007-2951)
- CVE url paths should be valid with cve prefix too (e.g. https://LP.../bugs/cve/cve-2007-2951
|
|
| 2007-07-04 15:13:26 |
Diogo Matsubara |
title |
CVE links should use CVE-YYYY-NNNN format |
All places mentioning CVE indexes should use CVE-YYYY-NNNN format |
|
| 2007-07-04 15:14:02 |
Diogo Matsubara |
malone: status |
Incomplete |
Confirmed |
|
| 2007-07-04 15:14:02 |
Diogo Matsubara |
malone: statusexplanation |
Hi Kees,
I guess you mean the CVE reference box in a bug page, right? Is there any other place that needs updating?
Thanks for the report. |
Kees, thanks for the list. I've udpated the bug description. |
|
| 2009-10-15 14:49:10 |
Curtis Hovey |
tags |
fix-it-friday ui |
ui |
|
| 2009-10-20 18:51:41 |
Kees Cook |
tags |
ui |
platform-want ui |
|
| 2010-12-26 18:45:39 |
Curtis Hovey |
launchpad: status |
Confirmed |
Triaged |
|
| 2010-12-26 18:45:42 |
Curtis Hovey |
launchpad: importance |
Undecided |
Low |
|
| 2010-12-26 18:45:54 |
Curtis Hovey |
tags |
lp-bugs platform-want ui |
confusing-ui lp-bugs platform-want ui |
|
| 2011-04-09 06:17:36 |
Robert Collins |
summary |
All places mentioning CVE indexes should use CVE-YYYY-NNNN format |
CVE fmt: uses YYYY-NNNN format which is wrong: should use CVE-YYYY-NNNN format |
|
| 2011-04-09 06:18:03 |
Robert Collins |
description |
When linking or displaying CVEs, Malone needs to make sure the name is correctly shown/parsed as CVE-YYYY-NNNN, so that search engines will be able to make sense of the links. The correct naming convention for CVEs is that they must start with "CVE". Currently, all the links show just YYYY-NNNN.
Other places that would be useful to use the convetion:
- "Link to CVE" page needs to take full CVE name, including "CVE-" prefix
- "CVE Reference" box for bugs that have linked CVEs
- CVE page needs missing dash between "CVE" and index number (e.g. lhttps://bugs.launchpad.net/bugs/cve/2007-2951)
- CVE url paths should be valid with cve prefix too (e.g. https://LP.../bugs/cve/cve-2007-2951
|
When linking or displaying CVEs, Malone needs to make sure the name is correctly shown/parsed as CVE-YYYY-NNNN, so that search engines will be able to make sense of the links. The correct naming convention for CVEs is that they must start with "CVE". Currently, all the links show just YYYY-NNNN.
Other places that would be useful to use the convetion:
- "Link to CVE" page needs to take full CVE name, including "CVE-" prefix
- "CVE Reference" box for bugs that have linked CVEs
- CVE page needs missing dash between "CVE" and index number (e.g. lhttps://bugs.launchpad.net/bugs/cve/2007-2951)
- CVE url paths should be valid with cve prefix too (e.g. https://LP.../bugs/cve/cve-2007-2951
searches need to support CVE-YYYY-NNNN too. |
|
