You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "john eipe (Jira)" <ji...@apache.org> on 2020/07/04 16:39:00 UTC
[jira] [Commented] (FC-286) To Apache Log4j 2
[ https://issues.apache.org/jira/browse/FC-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151360#comment-17151360 ]
john eipe commented on FC-286:
------------------------------
[~smckinney] I have made the changes on a clone on john77eipe.
[https://github.com/john77eipe/directory-fortress-core]
[https://github.com/john77eipe/directory-fortress-enmasse]
[https://github.com/john77eipe/directory-fortress-commander]
[https://github.com/john77eipe/directory-fortress-realm]
The tests ran fine after the changes. Please let me know how to proceed to pull request or any other strategy to push this in.
> To Apache Log4j 2
> -----------------
>
> Key: FC-286
> URL: https://issues.apache.org/jira/browse/FC-286
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 2.0.5
> Reporter: Shawn McKinney
> Assignee: Shawn McKinney
> Priority: Major
> Fix For: 3.0.0-RC1
>
>
> Upgrade to Log4j 2, due to vulnerabilities such as:
> [https://github.com/advisories/GHSA-2qrg-x229-3v8q]
>
> in the old libs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org