gianm opened a new pull request #12061: URL: https://github.com/apache/druid/pull/12061
Log4j 2.16.0 has a few changes that is further hardened and makes it impossible for users to stumble into a vulnerable configuration. I don't think this is a fire-drill update, because Druid 0.22.1+ with Log4j 2.15.0 is not vulnerable in its default configuration. (We don't ship with any JNDI features enabled.) But the additional hardening would be beneficial to our users. See announcement at: https://lists.apache.org/thread/t72msv9cpxw9q5zw8rfkhx52v24z57f1 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
