[
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.
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:
[
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),
[
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
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
[
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...
[
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
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
[
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
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
[
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
--
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]
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
13 matches
Mail list logo