You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@zookeeper.apache.org by bu...@apache.org on 2016/01/25 10:44:13 UTC
svn commit: r978535 - in /websites/staging/zookeeper/trunk/content: ./
security.html
Author: buildbot
Date: Mon Jan 25 09:44:13 2016
New Revision: 978535
Log:
Staging update by buildbot for zookeeper
Modified:
websites/staging/zookeeper/trunk/content/ (props changed)
websites/staging/zookeeper/trunk/content/security.html
Propchange: websites/staging/zookeeper/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 25 09:44:13 2016
@@ -1 +1 @@
-1726525
+1726600
Modified: websites/staging/zookeeper/trunk/content/security.html
==============================================================================
--- websites/staging/zookeeper/trunk/content/security.html (original)
+++ websites/staging/zookeeper/trunk/content/security.html Mon Jan 25 09:44:13 2016
@@ -55,11 +55,9 @@
<div class="wiki-content">
<h1>ZooKeeper Security</h1>
-<p>The Apache Software Foundation takes security issues very seriously. Due to the infrastructure nature of the Apache ZooKeeper project specifically, we haven't had many reports over time, but it doesn't mean that we haven't had concerns over some bugs and vulnerabilities. If you have any concern or believe you have uncovered a vulnerability, we suggest that you get in touch via the e-mail address <a href="mailto:security@zookeeper.apache.org?Subject=[SECURITY] My security issue" target="_top">security@zookeeper.apache.org</a>. In the message, try to provide a description of the issue and ideally a way of reproducing it. </p>
+<p>The Apache Software Foundation takes security issues very seriously. Due to the infrastructure nature of the Apache ZooKeeper project specifically, we haven't had many reports over time, but it doesn't mean that we haven't had concerns over some bugs and vulnerabilities. If you have any concern or believe you have uncovered a vulnerability, we suggest that you get in touch via the e-mail address <a href="mailto:security@zookeeper.apache.org?Subject=[SECURITY] My security issue" target="_top">security@zookeeper.apache.org</a>. In the message, try to provide a description of the issue and ideally a way of reproducing it. Note that this security address should be used only for undisclosed vulnerabilities. Dealing with fixed issues should be handled regularly via the user and the dev lists. <b>Please report any security problems to the project security address before disclosing it publicly.</b> </p>
-<p>The <span class="caps">ASF</span> Security team maintains a page with a description of how vulnerabilities are handled, check their <a href="http://www.apache.org/security/">Web page</a>). You may alternatively contact them first the report your potential vulnerability on <a href="mailto:security@apache.org" target="_top">security@apache.org</a>. Note that both security addressed should be used only for undisclosed vulnerabilities. Dealing with fixed issues should be handled regularly via the user and the dev lists.</p>
-
-<p><b>Please report any security problems to either the project security address or the <span class="caps">ASF </span>security team before disclosing it publicly.</b></p>
+<p>The <span class="caps">ASF</span> Security team maintains a page with a description of how vulnerabilities are handled, check their <a href="http://www.apache.org/security/">Web page</a> for more information. </p>
</div>
</td>
<td valign="top">