[DERBY-4325] Add a property that forces testEncryptionKeyLenths to run with key lengths 192 and 256

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.6.1.0
• Component/s: Test
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 28/Jul/09 18:44
• Updated: 06/Aug/09 20:15

Description

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.

Issue Links

• relates to: DERBY-3710 cannot access a database using AES encryption with encryptionKeyLength=192 after it's been shutdown