Document usage of a security manager for remote tests #406
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
The text was updated successfully, but these errors were encountered:
@@ Coverage Diff @@ ## trunk #406 +/- ## ============================================ + Coverage 58.58% 58.58% +<.01% Complexity 10616 10616 ============================================ Files 1193 1193 Lines 75957 75957 Branches 7343 7343 ============================================ + Hits 44499 44502 +3 + Misses 28953 28951 -2 + Partials 2505 2504 -1
Closes apache#406 on github git-svn-id: https://svn.apache.org/repos/asf/jmeter/trunk@1844855 13f79535-47bb-0310-9956-ffa450edef68 Former-commit-id: fb6bebb