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 88D4FDA30 for ; Sat, 22 Sep 2012 04:24:12 +0000 (UTC) Received: (qmail 12233 invoked by uid 500); 22 Sep 2012 04:24:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 11814 invoked by uid 500); 22 Sep 2012 04:24:09 -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 11703 invoked by uid 99); 22 Sep 2012 04:24:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 04:24:07 +0000 Date: Sat, 22 Sep 2012 15:24:07 +1100 (NCT) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Message-ID: <1545713301.110558.1348287847989.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DERBY-4229) encryptionKeyLength connection attribute should be documented 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-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461022#comment-13461022 ] Dag H. Wanvik commented on DERBY-4229: -------------------------------------- > The encryptionKeyLength=length attribute may also be combined with the encryptionProvider=providerName > and/or encryptionAlgorithm=algorithm attributes. You may wish to use encryptionKeyLength=length when > you specify a non-default encryption algorithm. If seems you'd want to use eKL only iff a) one wants a non default algorithm (default is DES) and b) the algorithm allows for more than one key length (AES is mentioned above) and c) one want a key length that is not default (AES 192 or 256 above). We should investigate your other questions, Kim, good ones! > encryptionKeyLength connection attribute should be documented > ------------------------------------------------------------- > > Key: DERBY-4229 > URL: https://issues.apache.org/jira/browse/DERBY-4229 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.5.1.1 > Reporter: Kathey Marsden > Assignee: Kim Haase > Fix For: 10.5.2.0 > > Attachments: cdevcsecure67151.html, DERBY-4229-2.diff, DERBY-4229-2.stat, DERBY-4229.diff, rrefattribencryptkeylength.html > > > The developer guide says: > The length of the encryption key depends on the algorithm used: > AES (128, 192, and 256 bits) > DES (the default) (56 bits) > DESede (168 bits) > All other algorithms (128 bits) > Note: The boot password should have at least as many characters as number of bytes in the encryption key (56 bits=8 bytes, 168 bits=24 bytes, 128 bits=16 bytes). The minimum number of characters for the boot password allowed by Derby is eight. > For AES, however, it does not tell how to change the default key length of 128. This can be changed with the encryptionKeyLength connection attribute. The documentation should also specify that special policy files for the JRE may be necessary to accomodate the longer length. > Also note that there is an outstanding issue DERBY-3710 regarding length of 192 for AES. -- 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