zookeeper-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r978483 - in /websites/staging/zookeeper/trunk/content: ./ security.html
Date Sun, 24 Jan 2016 18:02:25 GMT
Author: buildbot
Date: Sun Jan 24 18:02:25 2016
New Revision: 978483

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 Sun Jan 24 18:02:25 2016
@@ -1 +1 @@
-1726522
+1726523

Modified: websites/staging/zookeeper/trunk/content/security.html
==============================================================================
--- websites/staging/zookeeper/trunk/content/security.html (original)
+++ websites/staging/zookeeper/trunk/content/security.html Sun Jan 24 18:02:25 2016
@@ -55,23 +55,12 @@
           <div class="wiki-content">
  <h1>ZooKeeper Security</h1>
 
-<p>The Apache Software Foundation takes security issues very seriously. Due to the
infrastructure<br />
-nature of the Apache ZooKeeper project specifically, we haven't had many reports over time,
but<br />
-it doesn't mean that we haven't had concerns over some bugs and vulnerabilities. If you have
any<br />
-concern or believe you have uncovered a vulnerability, we suggest that you get in touch via
the<br />
-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<br />
-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. </p>
 
-<p>The <span class="caps">ASF</span> Security team maintains a page with
a description of how vulnerabilities are handled, <br />
-check their <a href="http://www.apache.org/security/">Web page</a>). You may
alternatively contact<br />
-them first the report your potential vulnerability on<br />
-<a href="mailto:security@apache.org" target="_top">security@apache.org</a>. Note
that both security<br />
-addressed should be used only for undisclosed vulnerabilities. Dealing with fixed issues
should <br />
-be handled regularly via the user and the dev lists.</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>_Please report any security problems to either the project security address or to
the <span class="caps">ASF </span>security<br />
-team before disclosing it publicly._</p>
+<p><em>Please report any security problems to either the project security address
or to the <span class="caps">ASF </span>security<br />
+team before disclosing it publicly.</em></p>
           </div>
         </td>
         <td valign="top">



Mime
View raw message