title: java.lang.SecurityException: The jurisdiction policy files are not signed by a trusted signer
body: <p>In working on a different problem (related to RMI), I upgraded the system's "security folder" with the "unlimited strength" policy files and now my applicaiton fails in a different way. I get a long stack dump, of which following bits appear pertinent:</p>
  
  <pre><code>Exception in thread "main" java.lang.ExceptionInInitializerError
  
  [...crop...]
  
  Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
          at javax.crypto.JceSecurity.&lt;clinit&gt;(JceSecurity.java:86)
          ... 17 more
  Caused by: java.lang.SecurityException: The jurisdiction policy files are not signed by a trusted signer!
  
  [...crop...]
  </code></pre>
  
  <p>Um, WTF? The ONLY change was that I moved the orignal jar files aside and added the unlimited ones in $JAVA_HOME/lib/security. That directory now looks like this:</p>
  
  <pre><code>$ ls
  blacklist      javaws.policy               trusted.libraries
  cacerts        local_policy.jar            US_export_policy.jar
  java.policy    local_policy.jar.strong     US_export_policy.jar.strong
  java.security  local_policy.jar.unlimited  US_export_policy.jar.unlimited
  </code></pre>
  
  <p>Of course, the .strong and .unlimited version are there so I can switch back quickly.</p>
  
  <p>The directions were short and plain, and it would appear that they ONLY envision the replacement of these two files (local_policy.jar and US_exportpolicy.jar).</p>
  
  <p>What else is there to do?</p>
  
  <p>Note that the versions of java and the policy files are the very youngest to date: 1.7.0_03, and jce_policy-6, respectively.</p>
  
  <p>P.S. The article of similar title, found <a href="https://stackoverflow.com/questions/1443871/jurisdiction-policy-files-are-not-signed-by-trusted-signers">here</a>, was of no help at all.</p>