[GitHub] [logging-log4j1] lsimons commented on pull request #17: Cleaned-up log4j 1.2 that disables scary networking (base=1.2.17, fully binary compatible)

lsimons commented on pull request #17: URL: https://github.com/apache/logging-log4j1/pull/17#issuecomment-1017491386 See * https://reload4j.qos.ch/ * https://github.com/qos-ch/reload4j for a maintained/released fork with similar security fixes. -- This is an automated message

[GitHub] [logging-log4j1] lsimons commented on pull request #17: Cleaned-up log4j 1.2 that disables scary networking (base=1.2.17, fully binary compatible)

lsimons commented on pull request #17: URL: https://github.com/apache/logging-log4j1/pull/17#issuecomment-1003669830 Superceded by #18 -- 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 specif

[GitHub] [logging-log4j1] lsimons commented on pull request #17: Cleaned-up log4j 1.2 that disables scary networking (base=1.2.17, fully binary compatible)

lsimons commented on pull request #17: URL: https://github.com/apache/logging-log4j1/pull/17#issuecomment-1003669519 The rationale is not found here because most discussion about what should happen with apache projects happens on mailing lists. In this case, the discussion can be followed