You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Chris Nauroth (Jira)" <ji...@apache.org> on 2022/10/21 21:27:00 UTC

[jira] [Assigned] (ZOOKEEPER-4626) Replace log4j 1.x with reload4j

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

Chris Nauroth reassigned ZOOKEEPER-4626:
----------------------------------------

    Assignee: Dagang Wei

Dataproc recently made this change internally. We can prepare the patch for contribution. CC: [~functicons].

> Replace log4j 1.x with reload4j
> -------------------------------
>
>                 Key: ZOOKEEPER-4626
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4626
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 3.8.0, 3.7.1
>            Reporter: Sanjay Kumar Sahu
>            Assignee: Dagang Wei
>            Priority: Major
>
> log4j 1 was replaced with reload4j which is fork of log4j 1.2.17 with the goal of fixing pressing security issues.
> As proposed in the dev mailing list ([https://lists.apache.org/thread/fdzkv80mzkf3w74z9120l0k0rc3v7kqk]) let's replace log4j 1 with reload4j .



--
This message was sent by Atlassian Jira
(v8.20.10#820010)