JDK-8212047 : Release Note: disallow and allow Options for java.security.manager System Property
- Type: Sub-task
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 12
- Priority: P2
- Status: Closed
- Resolution: Delivered
- Submitted: 2018-10-11
- Updated: 2019-04-05
- Resolved: 2018-10-11
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 12 |
|---|
12Resolved  |
Description
New "disallow" and "allow" token options have been added to the `java.security.manager` system property. In the JDK implementation, if the Java Virtual Machine starts with the system property `java.security.manager` set to "disallow", then the `System.setSecurityManager` method cannot be used to set a security manager and will throw an `UnsupportedOperationException`. The "disallow" option can improve run-time performance for applications that never set a security manager. For further details on the behavior of these options, see the class description of `java.lang.SecurityManager`.
Comments
|