This is an automated email from the ASF dual-hosted git repository.
menghaoran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 103e0d1 Update _index.en.md (#12261)
103e0d1 is described below
commit 103e0d1e7a998f292c2ad0eb7d30d2e298a870bd
Author: y2so <[email protected]>
AuthorDate: Tue Sep 7 17:08:38 2021 +0800
Update _index.en.md (#12261)
Improve the content
---
docs/community/content/security/_index.en.md | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/docs/community/content/security/_index.en.md
b/docs/community/content/security/_index.en.md
index 9827e8e..7d824be 100644
--- a/docs/community/content/security/_index.en.md
+++ b/docs/community/content/security/_index.en.md
@@ -1,15 +1,18 @@
+++
pre = "<b>4. </b>"
-title = "security"
+title = "Security"
weight = 4
chapter = true
+++
The Apache Software Foundation takes a rigorous stance on eliminating security
issues in its software projects.
-Apache ShardingSphere is also very concerned Security issues related to its
features and functionality.
+Likewise, Apache ShardingSphere is also vigilant and takes security issues
related to its features and functionality into the highest consideration.
-If you have apprehensions regarding ShardingSphere’s security or you discover
vulnerability or potential threat, don’t hesitate to get in touch with the
[Apache Security Team](http://www.apache.org/security/) by dropping a mail at
[[email protected]](mailto:[email protected]).
-Please specify the project name as ShardingSphere and its product name
ShardingSphere-JDBC or ShardingSphere-Proxy in the email and provide a
description of the relevant problem or potential threat.
-You are also urged to recommend the way to reproduce and replicate the issue.
The apache security team and the ShardingSphere community will get back to you
after assessing and analysing the findings.
+If you have any concerns regarding ShardingSphere’s security, or you discover
a vulnerability or potential threat, please don’t hesitate to get in touch with
the [Apache Security Team](http://www.apache.org/security/) by dropping an
email at [[email protected]](mailto:[email protected]).
-**please pay attention** to report the security issue on the security email
before disclosing it on public domain.
+Please specify the project name as "ShardingSphere" and its product name
"ShardingSphere-JDBC" or "ShardingSphere-Proxy" in the email, and provide a
description of the relevant problem or potential threat.
+You are also urged to recommend how to reproduce and replicate the issue.
+
+The Apache Security Team and the ShardingSphere community will get back to you
after assessing and analyzing the findings.
+
+**Please note** that the security issue should be reported on the security
email first, before disclosing it on any public domain.
