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 "Dinuka Kodithuwakku (JIRA)" <ji...@apache.org> on 2017/09/25 05:12:00 UTC

[jira] [Assigned] (DERBY-5538) Derby should use char[] to internally represent passwords, rather than String.

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

Dinuka Kodithuwakku reassigned DERBY-5538:
------------------------------------------

    Assignee: Dinuka Kodithuwakku

> 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
>            Assignee: Dinuka Kodithuwakku
>              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 was sent by Atlassian JIRA
(v6.4.14#64029)