IMPLEMENTATION TASKS:
* Create the mailing list (and check that it works from outside)
Signed-off-by: Ian Jackson <ijack...@chiark.greenend.org.uk>
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
---
v2: Provide whole email address for predisclosure-applications@,
but obfuscate it with <dot> and a <span>.
Reword sentence about public mailing list as suggested by
Ian Campbell.
---
security_vulnerability_process.html | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/security_vulnerability_process.html
b/security_vulnerability_process.html
index de5e83e..8870f8d 100644
--- a/security_vulnerability_process.html
+++ b/security_vulnerability_process.html
@@ -228,8 +228,10 @@ permitted to also make available the allocated CVE number.
This is no
longer permitted in accordance with MITRE policy.</p>
<h3>Predisclosure list membership application process</h3>
<p>Organisations who meet the criteria should contact
-security@xenproject if they wish to receive pre-disclosure of
-advisories. Please include in the e-mail:</p>
+predisclosure-applications@xenproject<d<span>ot</span>>org
+(which is a public mailing list) if they wish to receive
+pre-disclosure of advisories.
+<p>Please include in the e-mail:</p>
<ul>
<li>The name of your organization</li>
<li>A brief description of why you fit the criteria, along with
--
1.7.10.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
