[ http://issues.apache.org/jira/browse/DERBY-324?page=comments#action_66807 ] Myrna van Lunteren commented on DERBY-324: ------------------------------------------
>From this description I cannot find out if this is really ok behavior or not. If someone from Sun can pull some strings & find out it would help. If the behavior is OK, then we are seeing a false diff, and it could be worked around by modifying the store/aes_sed.properties file. Something like: currently: substitute=ERROR XJ001: Java exception: 'Keysize must;ERROR XJ001: Java exception: 'Wrong keysize: must change it to: substitute=ERROR XJ001: Java exception: 'Keysize must;ERROR XJ001: Java exception: 'Wrong keysize: must,ERROR XJ001: Java exception: 'AES key length must be 128, 192, or 256 bits: java.security.InvalidParameterException,ERROR XJ001: Java exception: 'Wrong keysize: must be equal to 128, 192 or 256: java.security.InvalidParameterException > AES encryption test fails on Solaris 10 > --------------------------------------- > > Key: DERBY-324 > URL: http://issues.apache.org/jira/browse/DERBY-324 > Project: Derby > Type: Bug > Components: Test > Versions: 10.1.0.0 > Environment: Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5. > Reporter: Olav Sandstaa > Priority: Minor > > The store/aes.sql test on Solaris 10 produces the following diff report: > *** Start: aes jdk1.4.2_02 2005-05-30 12:13:17 *** > 206 del > < ERROR XJ001: Java exception: 'Wrong keysize: must be equal to 128, 192 or > 256: java.security.InvalidParameterException'. > 206a206 > > ERROR XJ001: Java exception: 'AES key length must be 128, 192, or 256 bits: > > java.security.InvalidParameterException'. > Test Failed. > *** End: aes jdk1.4.2_02 2005-05-30 12:14:06 *** > The cause of this problem is that on most OSs, the > java.security.InvalidParameterException thrown by the JVM when an invalid > encryption key length is requested contains a message with the following text: > Wrong keysize: must be equal to 128, 192 or 256 > while on Solaris 10 the message contained in the exception has been changed > to: > AES key length must be 128, 192, or 256 bits > The reason for this is most likely that a different encryption library is > included in Solaris 10 compared > to the other OSs, either as part of the JVM or as a native library. > The problem occurs on Solaris 10 running on both x86 and Sparc processors. It > occurs both with jdk 1.4 and jdk 1.5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
