Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 24 Feb 2012 21:07:54 +0000 (UTC)
From: "Mamta A. Satoor (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1740585003.16788.1330117674058.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <799287238.12525.1323892890857.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5538) Derby should use char[] to internally
 represent passwords, rather than String.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-5538:
-----------------------------------

    Labels: derby_triage10_9  (was: )
    
> Derby should use char[] to internally represent passwords, rather than String.
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-5538
>                 URL: https://issues.apache.org/jira/browse/DERBY-5538
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.8.2.2
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_9
>
> I noticed that routines like AuthenticationServiceBase.encryptUsingDefaultAlgorithm() represent plaintext passwords as Strings. This is unsafe because Strings are easy to sniff even after they go out of scope. See the discussion on DERBY-866. We should rephrase passwords as char[] and zero them out as soon as possible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira