Description
The store/aes.sql test can, because it's a master-based test, only test what's guaranteed available, i.e. only the encryptionKeyLength=128.
If it were a junit test, we could make it ignore the expected failures if the larger key sizes weren't supported, but test otherwise.
Having a junit test doesn't guarantee the test would get executed, of course, but at least the test would exist.
Would it be useful/ok to have a message print to the console as a warning?
Attachments
Attachments
Issue Links
- relates to
-
DERBY-3710 cannot access a database using AES encryption with encryptionKeyLength=192 after it's been shutdown
- Closed
-
DERBY-4418 derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15 on Solaris
- Closed
-
DERBY-3720 Add documentation for the connection URL property encryptionKeyLength
- Closed