Differences in JCE policy files between java 1.4 and 1.5?

Question

I'm using a app that needs JCE unlimited strength policy files to start. Attempting to start with limited strength policy files with Java 1.4 installed will give:
java.security.InvalidKeyException: InitVerify error: java.lang.RuntimeException: engineGetKeySize() is not supported by this cipher!
however, running the same app on java 1.5 with limited strength policy files does not give this problem. I've checked http://java.sun.com/j2se/1.5.0/docs/guide/security/jce/JCERefGuide.html#AppE and http://java.sun.com/j2se/1.4.2/docs/guide/security/jce/JCERefGuide.html#AppE and the maximum allowed keysizes are identical. Has something else changed in the JCE policy files between these java versions? Can anyone tell me what's going on?

Answer 1

Incubus wrote:
say I have a code that does:
public void StringConcat(){
int noOfIter = 10000;
for(int i = 0; i < noOfIter; i++){
String s = "String " + i + " Being " + i + "concatenated " + i + "using " + i + "String" + i + "Builder";
If I compile this in 1.4 ( i.e using javac -source 1.4); the decompiled code looks the same.
But if I do so in 1.5 ( i.e if I decompile the same code compiled using javac -source 1.5), this is how it looks:
public void StringConcat(){
int noOfIter = 10000;
for(int i = 0; i < noOfIter; i++){
String s = (new StringBuilder).append("String ").append( i).append( " Being ").append( i).append( "concatenated ").append( i).append( "using ").append( i).append( "String").append( i).append( "Builder").toString();
The above was the compile time optimization I was talking about.What makes you think that the decompiler is not the problem?
The ONLY difference between 1.5 and 1.4 in that case is that one uses StringBuilder and one uses StringBuffer. And StringBuffer is faster.
Just wanted to know, are there any other differences in compile time optimizations between 1.4 and 1.5.I suggest that you go look at the read me. And I also suggest that you become familar with byte codes and stop assuming that a decompiler is going to tell you anything.