Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
MIME-Version: 1.0
In-Reply-To: <678007E4-B6C8-42C5-97FD-14DFEDF742D7@dslextreme.com>
References: <8EC30FDD-27CA-4B12-B08C-7B407E8DFC7E@chewy.com>
	<CACZkXPy50zKSekfg+LvDon7qWE_4w9zWNJK4XAZE80gAQMVa8g@mail.gmail.com>
	<8855C164-ED80-4E08-B91C-FAE1D90BA317@chewy.com>
	<CACZkXPwCqyU=eKBGz9kzn6hrkEo4cgGFBFvcDnBZ7LhDsmkJ_A@mail.gmail.com>
	<8939430E-B85B-4DEB-A49C-B32E99A771E5@chewy.com>
	<CACZkXPyMcMZKKtyOEZrN5xdtty_evecb-HL7PoUAg3kKFFSFKQ@mail.gmail.com>
	<678007E4-B6C8-42C5-97FD-14DFEDF742D7@dslextreme.com>
Date: Mon, 18 Jan 2016 20:41:25 -0800
Message-ID: 
 <CACZkXPyeWtF-H9ju1Es6_X236UnpiPdQ0QZ4g6nMJxJvbbaqBw@mail.gmail.com>
Subject: Re: RFC5424 over TCP without TLS
From: Gary Gregory <garydgregory@gmail.com>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=001a11402054753e530529a87b51

--001a11402054753e530529a87b51
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ah, right, so one can just configure a <SocketAppender> with a
<Rfc5424Layout> configured in a non-standard way with useTlsMessageFormat =
=3D
"false".

Gary

On Mon, Jan 18, 2016 at 8:35 PM, Ralph Goers <ralph.goers@dslextreme.com>
wrote:

> As I have stated before, that=E2=80=99s because the SyslogAppender is rea=
lly
> nothing more than the SocketAppender with one of the two Syslog Layouts
> hardwired to it.
>
> Ralph
>
> > On Jan 18, 2016, at 6:24 PM, Gary Gregory <garydgregory@gmail.com>
> wrote:
> >
> > Hm, yeah, you cannot pass a layout to a SyslogAppender. Dead end there.
> >
> > Gary
> >
> > On Mon, Jan 18, 2016 at 5:02 PM, Blake Day <blake@chewy.com <mailto:
> blake@chewy.com>> wrote:
> >
> >> So you mean a <SocketAppender>?  The layout is =E2=80=9Chardcoded=E2=
=80=9D on
> >> SyslogAppender.
> >>
> >>
> >>
> >>
> >> On 1/18/16, 7:42 PM, "Gary Gregory" <garydgregory@gmail.com> wrote:
> >>
> >>> What about using a <SyslogAppender> with a <Rfc5424Layout>?
> >>>
> >>> Gary
> >>>
> >>> On Mon, Jan 18, 2016 at 3:17 PM, Blake Day <blake@chewy.com> wrote:
> >>>
> >>>> It was worth a look, but no. SocketAppender creates an
> SslSocketManager
> >>>> when protocol =3D SSL.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On 1/18/16, 5:46 PM, "Gary Gregory" <garydgregory@gmail.com> wrote:
> >>>>
> >>>>> I think you might be able to "cheat" by saying protocol=3D"SSL" on =
the
> >>>>> appender...
> >>>>>
> >>>>> Gary
> >>>>>
> >>>>> On Mon, Jan 18, 2016 at 2:07 PM, Blake Day <blake@chewy.com> wrote:
> >>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> We are trying to achieve RFC5424 message formats over TCP transpor=
t
> >>>>>> without TLS.
> >>>>>>
> >>>>>> As you may know, SyslogAppender uses an instance of Rfc5424Layout =
to
> >>>>>> provide the logging layout.  That layout takes a parameter called
> >>>>>> =E2=80=9CuseTlsMessageFormat=E2=80=9D, which SyslogAppender sets b=
ased on whether
> >> TLS is
> >>>>>> configured.  When true, the layout wraps the log event in a
> >>>>>> TlsSyslogFrame.  TlsSyslogFrame simply prepends a length to the fu=
ll
> >> log
> >>>>>> message, but that length is required by syslog-ng to frame RFC5424
> >>>>>> messages.  While the RFC for TCP-based transport of the RFC5424
> >> format
> >>>> does
> >>>>>> not allow for non-TLS connections, some users (like us) would like
> to
> >>>> adopt
> >>>>>> the RFC5424 format over TCP *without* TLS.  We believe, but have n=
ot
> >>>>>> tested, that we could do this by simply adding a configuration
> >>>> parameter to
> >>>>>> the SyslogAppender that allows us to override useTlsMessageFormat =
to
> >>>> true.
> >>>>>>
> >>>>>> Any thoughts on this change?  Have we overlooked an obvious
> >> alternative
> >>>> to
> >>>>>> achieving RFC5424 over TCP without TLS?
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Michael Day
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> >>>>> Java Persistence with Hibernate, Second Edition
> >>>>> <http://www.manning.com/bauer3/>
> >>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> >>>>> Spring Batch in Action <http://www.manning.com/templier/>
> >>>>> Blog: http://garygregory.wordpress.com
> >>>>> Home: http://garygregory.com/
> >>>>> Tweet! http://twitter.com/GaryGregory
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> >>> Java Persistence with Hibernate, Second Edition
> >>> <http://www.manning.com/bauer3/>
> >>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> >>> Spring Batch in Action <http://www.manning.com/templier/>
> >>> Blog: http://garygregory.wordpress.com
> >>> Home: http://garygregory.com/
> >>> Tweet! http://twitter.com/GaryGregory
> >>
> >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com <mailto:garydgregory@gmail.com> |
> ggregory@apache.org <mailto:ggregory@apache.org>
> > Java Persistence with Hibernate, Second Edition
> > <http://www.manning.com/bauer3/ <http://www.manning.com/bauer3/>>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/ <
> http://www.manning.com/tahchiev/>>
> > Spring Batch in Action <http://www.manning.com/templier/ <
> http://www.manning.com/templier/>>
> > Blog: http://garygregory.wordpress.com <
> http://garygregory.wordpress.com/>
> > Home: http://garygregory.com/ <http://garygregory.com/>
> > Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
>


--=20
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--001a11402054753e530529a87b51--