[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

2013-08-08 Thread Andre Bogus (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733218#comment-13733218 ] Andre Bogus commented on LOG4J2-336: You're very welcome. Thanks for working on this.

[jira] [Created] (LOG4J2-337) SLF4JLogger attempts to cast an org.slf4j.Marker into an org.apache.logging.log4j.Marker, causing a ClassCastException

2013-08-08 Thread David Bidorff (JIRA)
David Bidorff created LOG4J2-337: Summary: SLF4JLogger attempts to cast an org.slf4j.Marker into an org.apache.logging.log4j.Marker, causing a ClassCastException Key: LOG4J2-337 URL:

[jira] [Updated] (LOG4J2-337) SLF4JLogger attempts to cast an org.slf4j.Marker into an org.apache.logging.log4j.Marker, causing a ClassCastException

2013-08-08 Thread David Bidorff (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bidorff updated LOG4J2-337: - Description: Every method of SLF4JLogger that uses Markers (including isTraceEnabled(Marker),

[jira] [Updated] (LOG4J2-337) SLF4JLogger attempts to cast an org.slf4j.Marker into an org.apache.logging.log4j.Marker, causing a ClassCastException

2013-08-08 Thread David Bidorff (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bidorff updated LOG4J2-337: - Description: Every method of SLF4JLogger that uses Markers, attempt to cast org.slf4j.Marker

Log Forgery and log4j

2013-08-08 Thread kommersz
Ladies and Gentleman, Recently I came across an issue with Log Forgery (http://cwe.mitre.org/data/definitions/117.html) - a problem where line feed characters passed over to logging results in extra log entries created when simple file-based logging is used. Checked briefly with log4j

[jira] [Closed] (LOG4J2-337) SLF4JLogger attempts to cast an org.slf4j.Marker into an org.apache.logging.log4j.Marker, causing a ClassCastException

2013-08-08 Thread David Bidorff (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bidorff closed LOG4J2-337. Resolution: Not A Problem My bad, I got it wrong: my MarkerFactory was poorly instantiated...

[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

2013-08-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733291#comment-13733291 ] Remko Popma commented on LOG4J2-336: Yes, this will be fixed with beta9. Not sure when

[jira] [Created] (LOG4J2-338) Add TLS support to SyslogAppender

2013-08-08 Thread Tibor Benke (JIRA)
Tibor Benke created LOG4J2-338: -- Summary: Add TLS support to SyslogAppender Key: LOG4J2-338 URL: https://issues.apache.org/jira/browse/LOG4J2-338 Project: Log4j 2 Issue Type: New Feature

[jira] [Comment Edited] (LOG4J2-338) Add TLS support to SyslogAppender

2013-08-08 Thread Tibor Benke (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733307#comment-13733307 ] Tibor Benke edited comment on LOG4J2-338 at 8/8/13 9:31 AM: It

[jira] [Created] (LOG4J2-339) Infinit loop in ThrowableProxy

2013-08-08 Thread Alexandr Dorogikh (JIRA)
Alexandr Dorogikh created LOG4J2-339: Summary: Infinit loop in ThrowableProxy Key: LOG4J2-339 URL: https://issues.apache.org/jira/browse/LOG4J2-339 Project: Log4j 2 Issue Type: Bug

[jira] [Resolved] (LOG4J2-339) Infinit loop in ThrowableProxy

2013-08-08 Thread Nick Williams (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-339. -- Resolution: Duplicate Infinit loop in ThrowableProxy --

Re: Log Forgery and log4j

2013-08-08 Thread Woonsan Ko
Maybe you can add a custom layout [1] plugin component [2]? I guess you can set a custom layout in appender configuration. [3] The layout seems responsible for producing final buffer to the output medium in the end. HTH, Woonsan [1]

Re: Log Forgery and log4j

2013-08-08 Thread Remko Popma
Gabor, I don't believe it is the responsibility of the logging library to protect against malicious input. Not only do I worry about the performance impact, I also don't think it is possible to protect against everything. A much better place to do this would be the application logic. Take the