[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131312#comment-16131312
]
Gary Gregory commented on LOG4J2-1896:
--------------------------------------
[[email protected]] and others:
I would like to close this issue and note that:
- We do not null out the char[] ivar which stores the password after it is used
since it could be needed again later. Intead, I will looking into adding a
clear() API that clears the field which can be used by call sites as they see
fit.
- We are not addressing encrypting or obfuscating char[] password in-place or
in a "vault".
Thoughts?
Gary
> Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String
> to char[] for passwords
> ---------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1896
> URL: https://issues.apache.org/jira/browse/LOG4J2-1896
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.9
>
>
> Update {{org.apache.logging.log4j.core.net.ssl.StoreConfiguration}} from a
> {{String}} to {{char[]}} to represent its password.
> The goal is to reduce the security risk of using a String for a password. See
> https://stackoverflow.com/questions/8881291/why-is-char-preferred-over-string-for-passwords
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
