Invalidkeyexception Illegal Key Size

Java Security: Illegal key size or default parameters?

Most likely you don't have the unlimited strength file installed now.

You may need to download this file:

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7 Download

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 Download (only required for versions before Java 8 u162)

Extract the jar files from the zip and save them in ${java.home}/jre/lib/security/.

InvalidKeyException Illegal key size

This error means that your Java virtual machine uses a policy that only allows restricted cryptography key sizes due to US export laws.

Java 9 and higher

The Unlimited Strength Jurisdiction Policy Files are included with Java 9 and used by default (see Security Updates in the Java 9 Migration Guide).

If you get this error with Java 9, it might mean the policy configuration has been changed to a more restrictive policy (limited), see the instructions from the migration guide:

JCE Jurisdiction Policy File Default is Unlimited

If your application previously required the Java Cryptography
Extension (JCE) Unlimited Strength Jurisdiction Policy Files, then you
no longer need to download or install them. They are included in the
JDK and are activated by default.

If your country or usage requires a more restrictive policy, the
limited Java cryptographic policy files are still available.

If you have requirements that are not met by either of the policy
files provided by default, then you can customize these policy files
to meet your needs.

See the crypto.policy Security property in the
<java-home>/conf/security/java.security file, or
Cryptographic Strength Configuration in the Java Platform,
Standard Edition Security Developer's Guide.

Java 8 and earlier

Java 8 Update 161 and higher

Starting with Java 8 Update 161, Java 8 defaults to the Unlimited Strength Jurisdiction Policy. If you receive this error, it could indicate the configuration has been changed to limited. See instructions in the next section on Java 8 Update 151, or the previous section on Java 9, for changing this back to unlimited.

Java 8 Update 151 and higher

Starting with Java 8 Update 151, the Unlimited Strength Jurisdiction Policy is included with Java 8 but not used by default. To enable it, you need to edit the java.security file in <java_home>/jre/lib/security (for JDK) or <java_home>/lib/security (for JRE). Uncomment (or include) the line

crypto.policy=unlimited

Make sure you edit the file using an editor run as administrator.

The policy change only takes effect after restarting the JVM (this is especially important for long-running server processes like Tomcat).

For backwards compatibility, installing the policy files as documented in the next section will still work as well.

Before Java 8 Update 151

For Java 8 Update 144 and earlier, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files (available at Oracle).

To install these files (from the README.txt in the download):

1. Download the unlimited strength JCE policy files.

2. Uncompress and extract the downloaded file.

   This will create a subdirectory called jce.
   This directory contains the following files:

   README.txt                   This file
   local_policy.jar             Unlimited strength local policy file
   US_export_policy.jar         Unlimited strength US export policy file
   

3. Install the unlimited strength policy JAR files.

   In case you later decide to revert to the original "strong" but
   limited policy versions, first make a copy of the original JCE
   policy files (US_export_policy.jar and local_policy.jar). Then
   replace the strong policy files with the unlimited strength
   versions extracted in the previous step.

   The standard place for JCE jurisdiction policy JAR files is:

   <java-home>/lib/security           [Unix]
   <java-home>\lib\security           [Windows]
   

Note for the JDK it is in jre/lib/security.

The new policy file only takes effect after restarting the JVM (this is especially important for long-running server processes like Tomcat).

java.security.InvalidKeyException: Illegal key size or default parameters in android

private String cryptKey = "qkjll5@2md3gs5Q@FDFqf";

By default Java supports only 128-bit encryption

128bits == 16Bytes == 16 Chars.

So cryptKey cannot exceed 16 characters.

If you want to exceed more than 16 character you have to install Java Cryptography Extension (JCE) Unlimited Strength.

Why 128bits?

Exception in thread main java.security.InvalidKeyException: Illegal key size

I think you need to install Java Cryptography Extension (JCE) the see important notes

https://bouncycastle.org/documentation.html

http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

InvalidKeyException : Illegal Key Size - Java code throwing exception for encryption class - how to fix?

So the problem must be with your JCE Unlimited Strength installation.

Be sure you overwrite the local_policy.jar and US_export_policy.jar in both your JDK's jdk1.6.0_25\jre\lib\security\ and in your JRE's lib\security\ folder.

In my case I would place the new .jars in:

C:\Program Files\Java\jdk1.6.0_25\jre\lib\security

and

C:\Program Files\Java\jre6\lib\security

---

If you are running Java 8 and you encounter this issue. Below steps should help!

Go to your JRE installation (e.g - jre1.8.0_181\lib\security\policy\unlimited) copy local_policy.jar and replace it with 'local_policy.jar' in your JDK installation directory (e.g - jdk1.8.0_141\jre\lib\security).

java.security.InvalidKeyException: Illegal key size although JCE Unlimited Strength Jurisdiction Policy is installed on Android Studio

Android Studio contains it's own JRE installation in the directory jre in it's installation dir.

However as you use Android Studio you are developing an Android app. The execution of an Android app does not use any JRE/JDK on your computer. It uses Dalvik on the device you use for testing your app.

Therefore this Android Studio internal JRE is only used for components that are executed directly on your computer, e.g. local tests or something similar.

---

Related Topics