Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 25237 invoked from network); 18 Dec 2009 18:02:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Dec 2009 18:02:41 -0000 Received: (qmail 99509 invoked by uid 500); 18 Dec 2009 18:02:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 99483 invoked by uid 500); 18 Dec 2009 18:02:41 -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 99475 invoked by uid 99); 18 Dec 2009 18:02:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 18:02:41 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 18:02:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 03BF1234C04C for ; Fri, 18 Dec 2009 10:02:19 -0800 (PST) Message-ID: <1608480644.1261159339001.JavaMail.jira@brutus> Date: Fri, 18 Dec 2009 18:02:19 +0000 (UTC) From: "Francois Orsini (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4483) Provide a way to change the hash algorithm used by BUILTIN authentication In-Reply-To: <526285707.1261139298094.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792551#action_12792551 ] Francois Orsini commented on DERBY-4483: ---------------------------------------- Note: Allowing to set a different hash algorithm would have to be done at the time the database is created when the hash password is stored in the database (storing the user property) as otherwise during runtime, one would not be able to compare some hash produced by the new configured hash algorithm versus the stored hash value which would have been generated using some previous and different algorithm. > Provide a way to change the hash algorithm used by BUILTIN authentication > ------------------------------------------------------------------------- > > Key: DERBY-4483 > URL: https://issues.apache.org/jira/browse/DERBY-4483 > Project: Derby > Issue Type: Improvement > Components: Services > Affects Versions: 10.5.3.0 > Reporter: Knut Anders Hatlen > Priority: Minor > > The BUILTIN authentication scheme protects the passwords by hashing them with the SHA-1 algorithm. It would be nice to have way to specify a different algorithm so that users can take advantage of new, stronger algorithms provided by their JCE provider if so desired. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.