You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by bu...@apache.org on 2015/07/17 16:58:18 UTC

svn commit: r958696 - in /websites/staging/httpd/trunk/content: ./ security/vulnerabilities-httpd.xml security/vulnerabilities_24.html

Author: buildbot
Date: Fri Jul 17 14:58:18 2015
New Revision: 958696

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml
    websites/staging/httpd/trunk/content/security/vulnerabilities_24.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 17 14:58:18 2015
@@ -1 +1 @@
-1691571
+1691585

Modified: websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml
==============================================================================
--- websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml (original)
+++ websites/staging/httpd/trunk/content/security/vulnerabilities-httpd.xml Fri Jul 17 14:58:18 2015
@@ -62,6 +62,9 @@ This issue was reported by Guido Vranken
 <affects prod="httpd" version="2.4.3"/>
 <affects prod="httpd" version="2.4.2"/>
 <affects prod="httpd" version="2.4.1"/>
+<acknowledgements>
+Régis Leroy
+</acknowledgements>
 </issue>
 
 <issue fixed="2.4.16" reported="20130805" public="20150609" released="20150715">

Modified: websites/staging/httpd/trunk/content/security/vulnerabilities_24.html
==============================================================================
--- websites/staging/httpd/trunk/content/security/vulnerabilities_24.html (original)
+++ websites/staging/httpd/trunk/content/security/vulnerabilities_24.html Fri Jul 17 14:58:18 2015
@@ -164,6 +164,11 @@ This issue was reported by Guido Vranken
 </p>
   </dd>
   <dd>
+    <p>Acknowledgements: 
+Régis Leroy
+</p>
+  </dd>
+  <dd>
   Reported to security team: 4th April 2015<br/>
   Issue public: 9th June 2015<br/></dd>
   <dd>