Skip to content

Commit

Permalink
JEP 411 deprecate java security manager
Browse files Browse the repository at this point in the history
  • Loading branch information
shawnmckinney committed Apr 16, 2021
1 parent 36e1d38 commit 0f35ad4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
Example shows how to use the Java Security Manager to prevent remote code execution exploits.

## Java Security Manager
* Due to the JEP below, the specific solution mentioned here of enabling the Java Security Manager is impracticable. However, its ideas, i.e. employing mandatory access control techniques are still very much applicable to this problem space.
* Due to JEP 411 (and other reasons already pointed out here), the specific solution mentioned of enabling the Java Security Manager is impractical. However, its ideas, i.e. employing mandatory access control techniques still very much apply.
* [JEP 411: Deprecate the Security Manager for Removal](https://openjdk.java.net/jeps/411)

## Intro to the Problem
Expand Down

0 comments on commit 0f35ad4

Please sign in to comment.