Remove obsolete CVE request E-mail templates

Now that CVE requests are performed via MITRE's Web form, we no
longer use the E-mail templates we previously documented for this
purpose. Delete them to avoid confusion.

Change-Id: I57218b5972382e5fb6917eb1c34625ba0a89d976
This commit is contained in:
Jeremy Stanley 2018-09-06 22:41:27 +00:00
parent 51e04ea771
commit 8dc2873ac7
1 changed files with 0 additions and 51 deletions

View File

@ -435,57 +435,6 @@ open-ended:
Affects: <=8.1.0 and ==9.0.0
CVE request email (private issues)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
* *To:* CNA
* *Subject:* CVE request for vulnerability in OpenStack $PROJECT
::
A vulnerability was discovered in OpenStack (see below). In order to
ensure full traceability, we need a CVE number assigned that we can
attach to private and public notifications. Please treat the
following information as confidential until further public
disclosure.
$DESCRIPTION
Thanks in advance,
--
$VMT_COORDINATOR_NAME
OpenStack Vulnerability Management Team
Email must be GPG-signed and GPG-encrypted.
CVE request email (public issues)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
* *To:* oss-security@lists.openwall.com
* *Cc:* cve-assign@mitre.org
* *Subject:* CVE request for vulnerability in OpenStack $PROJECT
::
A vulnerability was discovered in OpenStack (see below). In order to
ensure full traceability, we need a CVE number assigned that we can
attach to further notifications. This issue is already public,
although an advisory was not sent yet.
$DESCRIPTION
References:
https://launchpad.net/bugs/$BUG
Thanks in advance,
--
$VMT_COORDINATOR_NAME
OpenStack Vulnerability Management Team
Email must be GPG-signed but not encrypted.
Downstream stakeholders notification email (private issues)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^