GitHub user FSchumacher opened a pull request:
https://github.com/apache/jmeter/pull/406
Document usage of a security manager for remote tests
## Description
Remote tests can be secured even further, when running with enabled
security manager.
## Motivation and Context
Especially RMI has gained more attraction by attackers, so give users
another tool to defend against attacks.
## How Has This Been Tested?
A simple test plan has been run remotely with the documented steps. To be
honest the documentation has been done after the tests. So it would be great if
more people can follow the documentation and try their tests.
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Delete as appropriate
-->
- Documentation
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
- [x] I have updated the documentation accordingly.
[style-guide]: https://wiki.apache.org/jmeter/CodeStyleGuidelines
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/FSchumacher/jmeter security-manager
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jmeter/pull/406.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #406
----
commit 5514943ac9c8c54277ab92ad4913ed379d27590d
Author: Felix Schumacher <felix.schumacher@...>
Date: 2018-10-13T11:15:51Z
Document usage of a security manager for remote tests
----
---
