[DERBY-3710] cannot access a database using AES encryption with encryptionKeyLength=192 after it's been shutdown

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.1.1
• Fix Version/s: 10.5.3.0, 10.6.1.0
• Component/s: Services
• Environment: reproduced with ibm's jdk 1.5 and 1.6, and sun's jdk15. ; AES encryption with encryptionKeyLength=192 requires unrestricted security policy jars on your jvm
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Data corruption
• Assignee: Richard N. Hillegas
• Reporter: Myrna van Lunteren
• Created: 04/Jun/08 22:12
• Updated: 13/Jan/11 21:36
• Resolved: 04/Aug/09 13:25

Description

Accessing a database created using encryptionAlgorithm: AES/CBC/NoPadding, and encryptionKeyLength=192 after it's been shutdown fails like so:
-----------------------
ERROR XJ040: Failed to start database 'encdbcbc_192', see the next exception for details.
ERROR XBM06: Startup failed. An encrypted database cannot be accessed without the correct boot password.
----------------------

This does not occur when you use encryptionKeyLength=128 (does not require unrestricted jars) nor encryptionKeyLength=256 (does require unrestricted policy jars).

Note: our test (in derbyall): store/aes.sql does not test this, firstly it doesn't test the larger sizes (because it would diff & fail unless you have been able to adjust your jvm's policy jars), and secondly it doesn't shutdown before reconnecting.

Issue Links

• is related to: DERBY-4325 Add a property that forces testEncryptionKeyLenths to run with key lengths 192 and 256
• is related to: DERBY-3711 convert store/aes.sql to junit test & add unrestricted test cases.
• relates to: DERBY-4418 derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15 on Solaris