JDK-8162882 : Permission merge issue in jdk.crypto.ucrypto module
- Type: Bug
- Component: security-libs
- Sub-Component: javax.crypto
- Affected Version: 9
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2016-08-01
- Updated: 2016-08-05
- Resolved: 2016-08-01
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 9 |
|---|
9 b130Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The fix for JDK-8159752 put back an older version of the policy permissions for the jdk.crypto.ucrypto module. The permissions for jrt:/jdk.crypto.ucrypto in java.policy had:
permission java.io.FilePermission "<<ALL FILES>>", "read";
but in the new default.policy it is only:
permission java.io.FilePermission
"${java.home}/conf/security/ucrypto-solaris.cfg", "read";
It was updated in the -addprovider RFE (JDK-8130302) a little while ago.