This is an automated email from the ASF dual-hosted git repository.
milamber pushed a commit to branch update-docs-v5.5-release
in repository https://gitbox.apache.org/repos/asf/jmeter.git
The following commit(s) were added to refs/heads/update-docs-v5.5-release by
this push:
new 60e2d2f7c2 Add Security Manager mention when running JMeter in
distributed environment
60e2d2f7c2 is described below
commit 60e2d2f7c236e11393015b2125ce580f32615391
Author: Milamber <[email protected]>
AuthorDate: Fri Feb 3 10:43:03 2023 +0100
Add Security Manager mention when running JMeter in distributed environment
Cherry-pick from commits 5ca8729b9acdc4f3e7ab603071d9f783a311ad1a and
69c1109d4ca2ad6495470c4ed4f423626b4e57bc from master branch on
update-docs-v5.5-release branch, rebuild of documentation, and copy the result
files on asf-site branch (jmeter-site repo)
---
xdocs/security.xml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/xdocs/security.xml b/xdocs/security.xml
index 2ccf4b296f..f42ed06216 100644
--- a/xdocs/security.xml
+++ b/xdocs/security.xml
@@ -16,6 +16,7 @@
~ limitations under the License.
-->
+<!DOCTYPE document>
<document>
<properties>
<title>Security</title>
@@ -33,6 +34,13 @@
evaluate untrusted jmx files, it is up to you to provide the
required isolation.
</p>
+ <p>
+ Still in the area of security, when JMeter is used in distributed
+ environment, we recommend setting up the security manager in order
+ to avoid any execution of malicious code on the distributed
+ architecture. See the <a
href="./usermanual/remote-test.html#security-manager">
+ Security-Manager documentation</a> for its implementation.
+ </p>
</section>
<section name="Reporting security issues">
<p>
