JDK-8160723 : Improve jurisdiction policy file signing exception
- Type: Enhancement
- Component: security-libs
- Sub-Component: javax.crypto
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-07-01
- Updated: 2016-10-13
- Resolved: 2016-07-04
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 7 | JDK 8 |
|---|---|
| 7u121Fixed | 8u112 b03Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Caused by: java.lang.SecurityException: The jurisdiction policy files are not
signed by a trusted signer!
at javax.crypto.JarVerifier.verifyPolicySigned(JarVerifier.java:289)
at javax.crypto.JceSecurity.loadPolicies(JceSecurity.java:318)
Above exception can often mean that the wrong version of jurisdiction policy files have been installed in the JDK. We should improve the exception message to hint at such an issue.