Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C11BED50F for ; Thu, 20 Sep 2012 21:36:07 +0000 (UTC) Received: (qmail 80502 invoked by uid 500); 20 Sep 2012 21:36:07 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 80474 invoked by uid 500); 20 Sep 2012 21:36:07 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 80467 invoked by uid 99); 20 Sep 2012 21:36:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Sep 2012 21:36:07 +0000 Date: Fri, 21 Sep 2012 08:36:07 +1100 (NCT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: <1402551827.104877.1348176967577.JavaMail.jiratomcat@arcas> In-Reply-To: <149996752.53793.1339180523251.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (DERBY-5805) More context for bootPassword and encryptionKey attributes would be helpful MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459982#comment-13459982 ] Kim Haase commented on DERBY-5805: ---------------------------------- Thanks, Dag. Indeed, the topic on encryptionKey has an example that uses exactly those attributes. So I think what is needed is to update the encryptionProvider and encryptionAlgorithm topics to mention that they work with either bootPassword or encryptionKey and to provide an example for each that uses encryptionKey. Do you have some tests that use a non-default encryptionAlgorithm? DES/CBC/NoPadding is the default, so there is really no need to specify it. I was thinking of changing the encryptionKey example to use AES, or something. > 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