[ http://issues.apache.org/jira/browse/DERBY-788?page=all ]
Kristian Waagan updated DERBY-788:
----------------------------------
Attachment: DERBY-788-1a.diff
DERBY-788-1a.stat
'DERBY-788-1a.diff' is a patch that replaces the 16 byte key with a 8 byte key
for the DES encryption algorithm used in the test 'store/encryptionKey.sql'.
The test still exercises the intended parts of the Derby code (according to my
own analysis and that of Sunitha). The patch makes the test stop failing on
Solaris10 (with security provider 'SunPCKS11-Solaris') .
One test case is changed; where it previously tested a key that was of
incorrect length (longer than 8 bytes, shorter than 16), it now tests an
incorrect key of the correct length. It is not possible to make the test pass
on Solaris10 with a key of incorrect length, because keys of length less than 8
bytes are caught by a check in the code, and keys longer than 8 bytes cause the
underlying security provider to fail ('SunPCKS11-Solaris'). This issue will be
addressed in DERBY-1001 (rewrite of test to a JUnit-test).
Ran derbyall on Solaris10, which resulted in 6 known errors (some are already
fixed according to the tinderbox test). 'store/encryptionKey.sql' passed.
> 'store/encryptionKey.sql' fails on Solaris 10
> ---------------------------------------------
>
> Key: DERBY-788
> URL: http://issues.apache.org/jira/browse/DERBY-788
> Project: Derby
> Type: Bug
> Components: Services, Test, Regression Test Failure
> Versions: 10.0.2.1, 10.1.1.2, 10.1.2.1
> Environment: Solaris 10 (generic hardware)
> Sun JDK 5.0 with the 'SunPCKS11-Solaris' Java Security provider
> Reporter: Kristian Waagan
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-788-1a.diff, DERBY-788-1a.stat
>
> The 'store/encryptionKey.sql' test fails on Solaris 10.
> Investigation revealed that the failure is caused by a difference in behavior
> between the 'SunPCKS11-Solaris' provider and other providers (tested with
> 'SunJCE' and 'IBMJCE').
> The initialization of the DES cipher fails because the 16 byte key (specified
> in the test) is not translated to a 8 byte DES key by
> SecretKeyFactory.translateKey(). This might be a bug in the provider (I don't
> know the spec). Enquiries are being made.
> The exception is being thrown from the constructor of
> 'impl.services.jce.JCECipherProvider'.
--
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
