Add a property that forces testEncryptionKeyLenths to run with key lengths 192
and 256
--------------------------------------------------------------------------------------
Key: DERBY-4325
URL: https://issues.apache.org/jira/browse/DERBY-4325
Project: Derby
Issue Type: Improvement
Components: Test
Affects Versions: 10.6.0.0
Reporter: Kathey Marsden
Priority: Minor
Currently the test testEncryptionKeyLengths will try to detect if unrestricted
policy jars are in place and will run tests with encryption key lengths of 192
and 256 if supported. If they are not it will print the following warning:
testEncryptionKeyLengths no unrestricted policy jars; cannot test AES encryption
with encryptionKeyLengths 192 nor 256
no unrestricted policy jars; cannot test AES encryption with encryptionKeyLength
s 192 nor 256
In some JVM configurations we always expect this test to run and pass. Since
there is no failure, it is easy to miss if this tests regresses as seems to be
currently happening in the IBM nightlies.
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/797858-suites.All_diff.txt
It would be good to have a property that forces the test to try these lengths
regardless of what it detects is supported so such failures will be more
obvious.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
