FranciscoBorges edited a comment on pull request #34895: URL: https://github.com/apache/spark/pull/34895#issuecomment-995647652
@srowen saying "The current release is not evidently vulnerable" and concluding you can still ship Log4J 1.X for months seems _beyond silly_. Your users need a patch release with Log4J 2.16, _that_ is what will allow one to say "not vulnerable". edit: a comma. -- 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]
