-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b03
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8163741 | 8u121 | Sean Coffey | P4 | Resolved | Fixed | b01 |
| JDK-8167900 | emb-8u121 | Sean Coffey | P4 | Resolved | Fixed | b01 |
| JDK-8160781 | 7u121 | Sean Coffey | P4 | Resolved | Fixed | b03 |
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.
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.
- backported by
-
JDK-8160781 Improve jurisdiction policy file signing exception
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8160553 nodemgr start up issue: jurisdiction policy files are not signed
-
- Closed
-
-
-
- Closed
-