When we file security bugs, we usually have a CVE ID in the Summary (sometimes there are ID's in the Description and comments). It would be nice if the CVE id's could be a link to MITRE's site. IE: CAN-XXXX-XXXX CVE-XXXX-XXXX http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-XXXX-XXXX
Testing CVE-1234-1234 CAN-1234-1234
That is awesome. Will it work if the id is in the Summary?
Not sure, at first it doesnt seem so beacuase the summary is html filtered to prevent cross site scripting attacks. I will need to look deeper and see if it can be done. Comments are easy cause there is already a nice interface for adding additional recipes for auto linking things.
If not, don't worry about it too much. I'll just make sure I put the CVE ID in a comment as well as the summary.
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2.
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and therefore this feature will need to be implemented against the new release. Updating bug version to 3.2.
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can. Thanks Bugzilla Development Team
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
*** This bug has been marked as a duplicate of bug 624597 ***