Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-324

AES encryption test fails on Solaris 10

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.1.1.0
    • Fix Version/s: 10.1.3.1, 10.2.1.6
    • Component/s: Test
    • Labels:
      None
    • Environment:
      Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5.

      Description

      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.

        Attachments

        1. aes_sol10.diff
          1 kB
        2. aes_sol10.stat
          0.1 kB

          Activity

            People

            • Assignee:
              olav Olav Sandstaa
              Reporter:
              olav Olav Sandstaa
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: