Hi all,
I know I'm not very active on this list, but I do monitor all of the traffic.
I'm totally in favor of the change. It makes sense, and the last thing we need
is to publish a mistake at the last minute because we're not willing to make a
small change so late in the game. Let's do it righ
13, 2006 2:45 AM
To: Miao Fuyou
Cc: syslog@lists.ietf.org
Subject: Re: [Syslog] Framing in syslog-transport-tls
On Wed, Dec 13, 2006 at 05:54:28PM +0800, Miao Fuyou wrote:
> My co-workers in university also encountered this issue when
> implementing syslog-tls, and used a mechanism simili
On Wed, Dec 13, 2006 at 05:54:28PM +0800, Miao Fuyou wrote:
> My co-workers in university also encountered this issue when implementing
> syslog-tls, and used a mechanism similiar to the one of Rainer to overcome
> it. As I am aware of, currently there are two syslog framing implementation
> and
, my
perception is careful implementater would have no problem, and a note for
reminding is enough.
Regards,
Miao
> -Original Message-
> From: Rainer Gerhards [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 13, 2006 4:34 PM
> To: syslog@lists.ietf.org
> Subject: [Sys
On Wed, Dec 13, 2006 at 09:33:38AM +0100, Rainer Gerhards wrote:
> FRAME-LEN is a variable length field. It specifies the length of the
> frame including the length of FRAME-LEN itself. This is no real problem
> for the receiver. On the sender side, however, it is a bit tricky. I
> need to obtain
Miao, WG,
I have partially implemented syslog-transport-tls in two different
programs (MonitorWare Agent and rsyslog). My focus was the framing, not
tls itself (I needed the new framing for some other functionality, but
that is a separate story). I would like to share my experience during
that imp
