RE: CVE ID Syntax Change and Options

• To: "'Christey, Steven M.'" <coley@mitre.org>
• Subject: RE: CVE ID Syntax Change and Options
• From: Mark J Cox <mjc@redhat.com>
• Date: Wed, 7 Nov 2012 09:30:49 +0000
• CC: "'cve-editorial-board-list (cve-editorial-board-list@lists.mitre.org)'"<cve-editorial-board-list@LISTS.MITRE.ORG>
• Delivery-Date: Wed Nov 7 04:33:09 2012
• In-Reply-To: <F4A3A6029AA9A54E8FA9BF5FB9834C791B112BC7@exch-hq-1.secunia.local>
• References: <FC72FC641B949240B947AC6F1F83FBAF0691E562@IMCMBX01.MITRE.ORG> <F4A3A6029AA9A54E8FA9BF5FB9834C791B112BC7@exch-hq-1.secunia.local>
• User-Agent: Unknown

We've written most of our tools to handle CVE-\d+-\d+ already, so "extra 
digits" is our preferred option, and out of those a preference would be a 
fixed number of digits with leading 0s to reduce c&p errors.

Thanks, Mark
--
Mark J Cox / Senior Director, Security Engineering, Red Hat

• Follow-Ups:
  • RE: CVE ID Syntax Change and Options
    • From: "Williams, James K" <James.Williams@ca.com>

• References:
  • CVE ID Syntax Change and Options
    • From: "Christey, Steven M." <coley@mitre.org>
  • RE: CVE ID Syntax Change and Options
    • From: Carsten Eiram <che@secunia.com>

• Prev by Date: RE: CVE ID Syntax Change and Options
• Next by Date: RE: CVE ID Syntax Change and Options
• Prev by thread: RE: CVE ID Syntax Change and Options
• Next by thread: RE: CVE ID Syntax Change and Options
• Index(es):
  • Date
  • Thread