[Xen-devel] [PATCH 2/6] Clarifications to predisclosure list subscription instructions

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

Specially:
  * Mention that subscriptions via the webterface do not work / are
    not honoured.
  * Mention the preference for role addresses only.

See <20448.49637.38489.246434@xxxxxxxxxxxxxxxxxxxxxxxx>, section
    "8. Predisclosure subscription process, and email address
        criteria"
---
 security_vulnerability_process.html |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/security_vulnerability_process.html 
b/security_vulnerability_process.html
index eff108a..ee42402 100644
--- a/security_vulnerability_process.html
+++ b/security_vulnerability_process.html
@@ -206,7 +206,9 @@ if(ns4)_d.write("<scr"+"ipt type=text/javascript 
src=/globals/mmenuns4.js><\/scr
        <li>The planned disclosure date</li>
     </ul></p>
 
-    <p>Organisations who meet the criteria should contact security@xen if they 
wish to receive pre-disclosure of advisories.</p>    
+    <p>Organisations who meet the criteria should contact security@xen if they 
wish to receive pre-disclosure of advisories. Organisations should not request 
subscription via the mailing list web interface, any such subscription requests 
will be rejected and ignored.</p>
+    <p>Normally we would prefer that a role address be used for each 
organisation, rather than one or more individual's direct email address. This 
helps to ensure that changes of personel do not end up effectively dropping an 
organisation from the list</p>
+
     <p>The pre-disclosure list will also receive copies of public advisories 
when they are first issued or updated.</p>
     
     <h3>Organizations on the pre-disclosure list:</h3>
-- 
1.7.10.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel