[
https://issues.apache.org/jira/browse/LOG4J2-2532?focusedWorklogId=184906&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-184906
]
ASF GitHub Bot logged work on LOG4J2-2532:
------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/19 17:37
Start Date: 14/Jan/19 17:37
Worklog Time Spent: 10m
Work Description: rgoers commented on issue #252: Fixed message length
with TLS and Syslog // fixes LOG4J2-2532
URL: https://github.com/apache/logging-log4j2/pull/252#issuecomment-454093120
It isn't documented correctly. The only doc for it is at
http://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/layout/Rfc5424Layout.html#createLayout(org.apache.logging.log4j.core.net.Facility,%20java.lang.String,%20int,%20boolean,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20boolean,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20boolean,%20org.apache.logging.log4j.core.layout.LoggerFields[],%20org.apache.logging.log4j.core.config.Configuration)
and I don't believe even that is correct. As I recall, either syslog-ng or
rsyslog accepts a message length prefix to allow you to have multi-line
messages. I don't think this option really has anything to do with TLS but I am
not sure. This was added in https://issues.apache.org/jira/browse/LOG4J2-338,
so it has nothing to do with RFC-5424.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 184906)
Time Spent: 0.5h (was: 20m)
Remaining Estimate: 0.5h (was: 40m)
> SyslogAppender with RFC5424 and TLS is prepending messagelength
> ---------------------------------------------------------------
>
> Key: LOG4J2-2532
> URL: https://issues.apache.org/jira/browse/LOG4J2-2532
> Project: Log4j 2
> Issue Type: Bug
> Components: Core, Layouts
> Affects Versions: 2.11.1
> Environment: Linux
> Reporter: Maximilian
> Priority: Blocker
> Original Estimate: 1h
> Time Spent: 0.5h
> Remaining Estimate: 0.5h
>
> If I want to log via Syslog (RFC5424) the logs seem to have the length of the
> message in front of the message which results in parser errors at the
> syslogserver.
> {{config:}}
> {{<?xml version="1.0" encoding="UTF-8"?>}}
> {{ <Configuration status="INFO">}}
> {{ <Appenders>}}
> {{ <Syslog name="local" host="localhost" port="10001" format="RFC5424"
> newLine="true" id="App" mdcId="9999">}}
> {{ <SSL>}}
> {{ <TrustStore location="trust.jks" password="testtest" />}}
> {{ </SSL>}}
> {{ </Syslog>}}
> {{ </Appenders>}}
> {{ <Loggers>}}
> {{ <Root level="debug">}}
> {{ <AppenderRef ref="local"/>}}
> {{ </Root>}}
> {{ </Loggers>}}
> {{ </Configuration> }}
> {{Result (with openssl s_server -key private.pem -cert public.pem -accept
> 10001):}}
> {{67 <134>1 2019-01-14T13:26:14.947+01:00 apu localhorst 12866 - - Test}}
> Expected result:
> {{<134>1 2019-01-14T13:26:14.947+01:00 apu localhorst 12866 - - Test}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
