You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2012/09/20 19:06:07 UTC
[jira] [Comment Edited] (DERBY-5805) More context for bootPassword
and encryptionKey attributes would be helpful
[ https://issues.apache.org/jira/browse/DERBY-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459735#comment-13459735 ]
Dag H. Wanvik edited comment on DERBY-5805 at 9/21/12 4:05 AM:
---------------------------------------------------------------
> However, the topics on encryptionProvider and encryptionAlgorithm do not mention the encryptionKey attribute, implying that they only work with bootPassword.
I see an example in the tests (in "encryptionKey_jar.sql") that combines algorithm and key:
connect 'jdbc:derby:jar:(ina.jar)db1;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=6162636465666768' AS DB1;
I believe encryptionKey can be used instead of bootPassword always.
[Update: the code in JCECipherFactory#init indicates this holds. -Dag ]
was (Author: dagw):
> However, the topics on encryptionProvider and encryptionAlgorithm do not mention the encryptionKey attribute, implying that they only work with bootPassword.
I see an example in the tests (in "encryptionKey_jar.sql") that combines algorithm and key:
connect 'jdbc:derby:jar:(ina.jar)db1;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=6162636465666768' AS DB1;
I believe encryptionKey can be used instead of bootPassword always.
> More context for bootPassword and encryptionKey attributes would be helpful
> ---------------------------------------------------------------------------
>
> Key: DERBY-5805
> URL: https://issues.apache.org/jira/browse/DERBY-5805
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.1.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
>
> The Developer's Guide and Reference Manual information on the bootPassword and encryptionKey attributes doesn't state (not prominently, anyway) that these properties are mutually exclusive, as Rick Hillegas points out in his 6/8/2012 comment on DERBY-5622. This information should be included in the documentation for these properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira