You are viewing a plain text version of this content. The canonical link for it is here.
- Re: [VOTE] Future of Log4j 1.x - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/01 15:18:39 UTC, 11 replies.
- Re: [DISCUSS][VOTE] Future of Log4j 1.x - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/01 15:37:37 UTC, 3 replies.
- [GitHub] [logging-log4j1] larrywest commented on pull request #17: Cleaned-up log4j 1.2 that disables scary networking (base=1.2.17, fully binary compatible) - posted by GitBox <gi...@apache.org> on 2022/01/01 17:18:56 UTC, 0 replies.
- [GitHub] [logging-log4j1] larrywest edited a comment on pull request #17: Cleaned-up log4j 1.2 that disables scary networking (base=1.2.17, fully binary compatible) - posted by GitBox <gi...@apache.org> on 2022/01/01 17:35:47 UTC, 0 replies.
- [GitHub] [logging-log4j1] larrywest commented on pull request #18: Refine build scripts - posted by GitBox <gi...@apache.org> on 2022/01/01 17:42:13 UTC, 0 replies.
- [GitHub] [logging-log4j1] vlsi commented on pull request #18: Refine build scripts - posted by GitBox <gi...@apache.org> on 2022/01/01 17:46:44 UTC, 0 replies.
- [GitHub] [logging-log4j1] rgoers commented on pull request #18: Refine build scripts - posted by GitBox <gi...@apache.org> on 2022/01/01 17:49:14 UTC, 0 replies.
- [log4cxx] Short filename options - posted by Robert Middleton <rm...@apache.org> on 2022/01/01 20:11:30 UTC, 6 replies.
- [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) - posted by GitBox <gi...@apache.org> on 2022/01/02 06:10:06 UTC, 2 replies.
- [GitHub] [logging-log4j1] lsimons closed pull request #17: Cleaned-up log4j 1.2 that disables scary networking (base=1.2.17, fully binary compatible) - posted by GitBox <gi...@apache.org> on 2022/01/02 06:13:56 UTC, 0 replies.
- [VOTE] CVE creation process - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/03 11:59:21 UTC, 10 replies.
- Re: Master branch - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/03 12:30:02 UTC, 6 replies.
- LOG4J2-3259 Limit max recursion depth when interpolating strings - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/03 12:41:12 UTC, 5 replies.
- [DISCUSS][VOTE] CVE creation process - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/03 15:49:00 UTC, 2 replies.
- [DISCUSS\[VOTE] CVE creation process - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/03 15:54:40 UTC, 0 replies.
- Re: [VOTE][LAZY] Release Apache Logging Parent POM version 5 - posted by Matt Sicker <bo...@gmail.com> on 2022/01/03 21:52:41 UTC, 0 replies.
- [VOTE] Release Log4j Scala API 12.1-rc1 - posted by Matt Sicker <bo...@gmail.com> on 2022/01/03 22:27:09 UTC, 0 replies.
- [log4cxx] next_stable and other fixes - posted by Robert Middleton <rm...@apache.org> on 2022/01/04 00:06:28 UTC, 2 replies.
- [RESULT][VOTE] Future of Log4j 1.x - posted by Christian Grobmeier <gr...@apache.org> on 2022/01/05 16:29:09 UTC, 0 replies.
- [ANNOUNCE] Log4j 1 End-of-Life Statement - posted by Ron Grabowski <rg...@apache.org> on 2022/01/06 00:23:47 UTC, 8 replies.
- [LOG4J 1] standardizing the Maven build - posted by Ceki Gülcü <ce...@qos.ch> on 2022/01/06 18:39:00 UTC, 5 replies.
- Re: [logging-log4j1] branch v1.2.8 created (now 0cde9dd) - posted by Gary Gregory <ga...@gmail.com> on 2022/01/06 21:21:03 UTC, 14 replies.
- [RESULT][VOTE] CVE creation process - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/07 10:21:17 UTC, 2 replies.
- Jira review - posted by Gary Gregory <ga...@gmail.com> on 2022/01/07 12:48:05 UTC, 3 replies.
- Properties Enhancement in Log4j 2 3.x - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/08 07:17:24 UTC, 1 replies.
- Copyright 1969? - posted by Gary Gregory <ga...@gmail.com> on 2022/01/08 10:52:31 UTC, 3 replies.
- [DISCUSS] Support 'log4j.rootLogger=INFO,Console' configuration grammar in log4j2 - posted by "张铎(Duo Zhang)" <pa...@gmail.com> on 2022/01/09 15:01:51 UTC, 16 replies.
- Google OSS-Fuzz - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/10 11:27:43 UTC, 3 replies.
- [LOG4J2-3319] Fragment vs bundle for log4j-1.2-api - posted by Gary Gregory <ga...@gmail.com> on 2022/01/11 12:30:32 UTC, 1 replies.
- Log4j1ConfigurationParser and log4j.appender.ConsoleLogger.Threshold - posted by "Sam.Mesh" <Sa...@gmail.com> on 2022/01/11 21:27:01 UTC, 2 replies.
- Re: [logging-log4j2] 02/02: Use final and simpler hashcode generation through Objects. - posted by Carter Kozak <ck...@ckozak.net> on 2022/01/12 13:59:25 UTC, 0 replies.
- Re: [logging-log4j2] 02/04: Our convention is to make test classes public. - posted by Matt Sicker <bo...@gmail.com> on 2022/01/12 18:07:25 UTC, 5 replies.
- Re: [CI][UNSTABLE] Logging/log4j/release-2.x#696 has test failures - posted by Gary Gregory <ga...@gmail.com> on 2022/01/12 18:36:00 UTC, 1 replies.
- Code Formatter? - posted by Carter Kozak <ck...@ckozak.net> on 2022/01/13 03:23:07 UTC, 5 replies.
- RE: Maven published jars not matching jars downloaded from apache.org? - posted by Jason Pyeron <jp...@pdinc.us> on 2022/01/13 08:58:34 UTC, 1 replies.
- Should lookups be split out or otherwise disabled by default? - posted by Matt Sicker <bo...@gmail.com> on 2022/01/14 03:19:33 UTC, 3 replies.
- Re: [Chainsaw] Removal of Log4j1 - posted by Robert Middleton <rm...@apache.org> on 2022/01/17 04:30:46 UTC, 2 replies.
- Re: [logging-log4j2] branch release-2.x updated (ff33bbc -> 97f9201) - posted by Carter Kozak <ck...@ckozak.net> on 2022/01/17 18:50:54 UTC, 7 replies.
- CI red - posted by Gary Gregory <ga...@gmail.com> on 2022/01/18 12:41:51 UTC, 4 replies.
- CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x - posted by Ralph Goers <rg...@apache.org> on 2022/01/18 14:42:17 UTC, 1 replies.
- CVE-2022-23305: SQL injection in JDBC Appender in Apache Log4j V1 - posted by Ralph Goers <rg...@apache.org> on 2022/01/18 14:42:35 UTC, 0 replies.
- CVE-2022-23307: Apache Log4j 1.x: A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution. - posted by Ralph Goers <rg...@apache.org> on 2022/01/18 14:42:56 UTC, 0 replies.
- Re: [logging-log4j2] 01/02: Add PropertiesLookup#getProperties(). - posted by Carter Kozak <ck...@ckozak.net> on 2022/01/19 23:31:47 UTC, 3 replies.
- [GitHub] [logging-log4j1] lsimons commented on pull request #18: Refine build scripts - posted by GitBox <gi...@apache.org> on 2022/01/20 13:09:39 UTC, 0 replies.
- [GitHub] [logging-log4j1] lsimons commented on pull request #15: vulnerability for Version 1.x. CVE-2021-4104 - posted by GitBox <gi...@apache.org> on 2022/01/20 13:10:42 UTC, 0 replies.
- [GitHub] [logging-log4j1] lsimons commented on pull request #16: Cleaned-up log4j 1.2 that disables scary networking (trunk, binary-incompatible) - posted by GitBox <gi...@apache.org> on 2022/01/20 13:11:25 UTC, 0 replies.
- Is log4j 2.12.4 - posted by anchit parmar <an...@idbiintech.com.INVALID> on 2022/01/20 14:12:17 UTC, 2 replies.
- Fwd: [apache/logging-log4j2] Bump tomcat-catalina from 8.5.20 to 10.0.14 (PR #662) - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/21 08:25:48 UTC, 13 replies.
- log4j-tools and log4j-maven-shade-plugin-extensions - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/21 16:42:03 UTC, 0 replies.
- Re: [CI][UNSTABLE] Logging/log4j/release-2.x#803 has test failures - posted by Matt Sicker <bo...@gmail.com> on 2022/01/22 22:37:37 UTC, 3 replies.
- Is a truly small core possible for 3.0? - posted by Gary Gregory <ga...@gmail.com> on 2022/01/26 13:07:08 UTC, 18 replies.
- LOG4J2-3260 Missing branch protection settings - posted by Volkan Yazıcı <vo...@yazi.ci> on 2022/01/26 20:25:23 UTC, 13 replies.
- Log4j 1.x replacement - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/27 17:33:36 UTC, 5 replies.
- I've disabled the Log4j2 Jenkins build for now - posted by Matt Sicker <bo...@gmail.com> on 2022/01/28 16:31:34 UTC, 3 replies.
- Build fails in Master - posted by Ralph Goers <ra...@dslextreme.com> on 2022/01/31 05:49:58 UTC, 8 replies.
- JDK 18 Rampdown Phase 2 & JDK 19 Early-Access Builds - posted by David Delabassee <da...@oracle.com> on 2022/01/31 09:29:02 UTC, 0 replies.