If you try to create an in-memory database with an illegal encryption key size,
you get an ASSERT failure rather than a diagnostic telling you that the key
size is unsupported.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-4329
URL: https://issues.apache.org/jira/browse/DERBY-4329
Project: Derby
Issue Type: Bug
Components: Store
Reporter: Rick Hillegas
The following script shows this problem for me when I use a Java 5 VM on Mac OS
X. The first connection (to an in-memory database) raises an assertion. In
contrast, the second connection (to an on-disk database) gives useful
diagnostics:
ij version 10.6
ij> connect
'jdbc:derby:memory:encdbcbc_256;create=true;dataEncryption=true;encryptionKeyLength=256;encryptionAlgorithm=AES/CBC/NoPadding;bootPassword=Thursday';
ERROR XJ001: Java exception: 'ASSERT FAILED serviceName =
memory:/Users/rh161140/derby/dummy/encdbcbc_256;storageFactory.getCanonicalName()
= /Users/rh161140/derby/dummy/encdbcbc_256:
org.apache.derby.shared.common.sanity.AssertFailure'.
ij> connect
'jdbc:derby:encdbcbc_256_disk;create=true;dataEncryption=true;encryptionKeyLength=256;encryptionAlgorithm=AES/CBC/NoPadding;bootPassword=Thursday';
ERROR XJ041: Failed to create database 'encdbcbc_256_disk', see the next
exception for details.
ERROR XBM01: Startup failed due to an exception. See next exception for
details.
ERROR XBCX0: Exception from Cryptography provider. See next exception for
details.
ERROR XJ001: Java exception: 'Illegal key size:
java.security.InvalidKeyException'.
ij
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
