You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2021/12/15 01:54:05 UTC

[GitHub] [druid] hzluyang commented on pull request #12061: Update to log4j 2.16.0.

hzluyang commented on pull request #12061:
URL: https://github.com/apache/druid/pull/12061#issuecomment-994214849


   "(We don't ship with any JNDI features enabled.)"  
   I don't want to upgrade druid verison, so I plan to delete jndilookup in older release like 0.20.1 to avoid this CVE-2021-44228 issue like this
   zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
   in  apache-druid-0.20.1/lib/log4j-core-2.8.2.jar
   
   this operation should be OK? will not affect the druid cluster functions?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org