You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Olav Sandstaa (JIRA)" <de...@db.apache.org> on 2005/05/30 16:03:54 UTC
[jira] Created: (DERBY-324) AES encryption test fails on Solaris 10
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
[jira] Closed: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=all ]
Olav Sandstaa closed DERBY-324:
-------------------------------
The AES encryption test runs without errors on Solaris 10.
> 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.1.0
> Environment: Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5.
> Reporter: Olav Sandstaa
> Assignee: Olav Sandstaa
> Priority: Minor
> Attachments: aes_sol10.diff, aes_sol10.stat
>
> 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
Re: [jira] Commented: (DERBY-324) AES encryption test fails on Solaris
10
Posted by Olav Sandstaa <Ol...@Sun.COM>.
Kathey Marsden wrote:
>Sometimes it is just easier and cleaner to rewrite the .sql test as a
>.java test and evaluate the results pro grammatically.
>
>
I agree. In most cases a .java test would be much more portable between
platforms and easier to maintain. But Dag gave me a hint of that I could
use regular expressions in the sed file, and replacing the comma with a
dot "." solved the problem.
Olav
Re: [jira] Commented: (DERBY-324) AES encryption test fails on Solaris
10
Posted by Kathey Marsden <km...@sbcglobal.net>.
Olav Sandstaa (JIRA) wrote:
> Any suggestions on how I can use the aes_sed.properties script to get rid of this or alternative ways to make the output from this test match the master file?
>
>
>
Sometimes it is just easier and cleaner to rewrite the .sql test as a
.java test and evaluate the results pro grammatically.
Kathey
[jira] Commented: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=comments#action_12313394 ]
Olav Sandstaa commented on DERBY-324:
-------------------------------------
I have tried to modify the aes_sed.properties file as suggested by Myrna. I had to trim down the size of the pattern/substitute parts to get rid of all the commas in the message strings. Unfortunately, I still have a problem with one comma. The original error message seen on most platforms contains the following sub-string:
128, 192 or 256
while the new message string seen on Solaris 10 contains an extra comma:
128, 192, or 256
Since neither the pattern nor the substitute part of the sed script are allowed to contain a comma, I am unable to get rid of the comma after 192. Any suggestions on how I can use the aes_sed.properties script to get rid of this or alternative ways to make the output from this test match the master file?
> 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
> Assignee: 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
[jira] Resolved: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=all ]
Bernt M. Johnsen resolved DERBY-324:
------------------------------------
Resolution: Fixed
comitted
> 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.1.0
> Environment: Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5.
> Reporter: Olav Sandstaa
> Assignee: Olav Sandstaa
> Priority: Minor
> Attachments: aes_sol10.diff, aes_sol10.stat
>
> 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
[jira] Reopened: (DERBY-324) AES encryption test fails on Solaris
10
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=all ]
Bernt M. Johnsen reopened DERBY-324:
------------------------------------
Merge to 10.1.3
> 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.1.0
> Environment: Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5.
> Reporter: Olav Sandstaa
> Assignee: Olav Sandstaa
> Priority: Minor
> Attachments: aes_sol10.diff, aes_sol10.stat
>
> 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
[jira] Commented: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=comments#action_66855 ]
Olav Sandstaa commented on DERBY-324:
-------------------------------------
I too think this behavior is OK. The message text returned with the exception basically gives the
same explaination for why the operation failed. There is no reason for why we can expect message
strings like this be the same between platforms.
I will test out the sed filter proposed by Myrna on a few Solaris 10 machines.
> 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
[jira] Commented: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Anonymous (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=all ]
updated DERBY-324:
-------------------
Attachment: aes_sol10.diff
aes_sol10.stat
> 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
> Assignee: Olav Sandstaa
> Priority: Minor
> Attachments: aes_sol10.diff, aes_sol10.stat
>
> 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
[jira] Closed: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=all ]
Bernt M. Johnsen closed DERBY-324:
----------------------------------
Fix Version: 10.2.0.0
10.1.3.0
Resolution: Fixed
Committed revision 406114 on 10.1 branch
> 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.1.0
> Environment: Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5.
> Reporter: Olav Sandstaa
> Assignee: Olav Sandstaa
> Priority: Minor
> Fix For: 10.2.0.0, 10.1.3.0
> Attachments: aes_sol10.diff, aes_sol10.stat
>
> 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
[jira] Commented: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=comments#action_12313813 ]
Olav Sandstaa commented on DERBY-324:
-------------------------------------
This patch fixes a problem in the AES test when running it on Solaris 10. The problem occurred due to a exception message text has been changed on Solaris 10. The problem is fixed by extending the substitute section of the aes_sed.properties file.
derbyall has been run on Solaris10 (sparc and x86) to verify that the problem is gone and on Solaris9 (sparc and x86) and Linux to verify that the change
does not influence on JVM producing the original error message text. Although some tests failed none of these seems related to this fix.
> 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
> Assignee: Olav Sandstaa
> Priority: Minor
> Attachments: aes_sol10.diff, aes_sol10.stat
>
> 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
[jira] Commented: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=comments#action_66808 ]
Sunitha Kambhampati commented on DERBY-324:
-------------------------------------------
The behavior is OK. I think its only error message diff needs to be sed out.
It would be great if someone who has access to the solaris machine/env where the diff occurred can test out by modifying the aes_sed.properties as Myrna suggested.
> 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
[jira] Assigned: (DERBY-324) AES encryption test fails on Solaris 10
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-324?page=all ]
Olav Sandstaa reassigned DERBY-324:
-----------------------------------
Assign To: Olav Sandstaa
> 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
> Assignee: 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