OMID-225 Migrate from log4j1 to reload4j #110
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Log4J1 is abandoned and has a number of significant CVEs filed for it. Reload4J (https://reload4j.qos.ch) is a drop in binary compatible replacement for Log4J1 with all known security issues remediated. Move up hbase.version to 2.4.13 and hadoop.version to 2.10.2 because those downstream versions have also migrated from log4j1 to reload4j.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Log4J1 is abandoned and has a number of significant CVEs filed for it. Reload4J is a drop in binary compatible replacement for Log4J1 with all known security issues remediated.
Move up
hbase.versionto 2.4.13 andhadoop.versionto 2.10.2 because those downstream versions have also migrated from log4j1 to reload4j.