[
https://issues.apache.org/jira/browse/LOG4J2-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602521#comment-17602521
]
ASF subversion and git services commented on LOG4J2-3548:
---------------------------------------------------------
Commit 60fe5d443770e788e02728d01487a69176c0fc45 in logging-log4j2's branch
refs/heads/dependabot/maven/io.fabric8-kubernetes-client-6.1.1 from Piotr P.
Karwasz
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=60fe5d4437 ]
[[LOG4J2-3548] Improve support of `null` location and password
Adds support for a `null` location and password (as required by e.g. the
"Windows-MY" keystore).
> Password-less key stores fail to initialise StoreConfiguration
> --------------------------------------------------------------
>
> Key: LOG4J2-3548
> URL: https://issues.apache.org/jira/browse/LOG4J2-3548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.18.0
> Reporter: Kristof Farkas-Pall
> Assignee: Piotr Karwasz
> Priority: Minor
> Fix For: 2.19.0
>
>
> In LOG4J2-3439 there was a change in AbstractKeyStoreConfiguration that
> replaces null passwords with a default value. This means that when
> password-less key stores initialized, the integrity is checked with the
> default password ("changeit"), which of course fails.
> I think the replacement should be reverted, to allow for password-less key
> stores to be initalized correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
