Rainer,
Stunnel is a secure wrapper for TCP stream. Actually delimiting Syslog is
done in the TCP part rather than TLS (or stunnel) part in Syslog-ng with
stunnel. One can use stunnel to secure any Syslog TCP transport, such as
rsyslog and kiwisyslog, and kiwisyslog does use CRLF for delimiting
Just to clarify, Kiwi Syslog V8 currently sends CRLF as the TCP delimiter,
but will accept LF, CR, CRLF, LFCR and NULL as valid delimiters on the
incoming stream. We will be changing our sending delimiter to LF in the near
future to make it more compatible with syslog-ng etc.
Cheers
Andrew
On Mon, 2006-08-14 at 12:20 +0200, tom.petch wrote:
- Original Message -
From: David Harrington [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 10, 2006 7:33 PM
Subject: [Syslog] timeline
1) whether draft-ietf-syslog-transport-tls should use byte-counting,
I vote for byte counting an no magic character.
I'm sorry for the backward compatibility problems this may
introduce, but things should move ahead, and providing a
solid standard is one of the best ways to do this.
John
Anton Okmianski (aokmians) [EMAIL PROTECTED] 8/11/2006 9:26 AM
Here
I've been mostly lurking lately, but I would like to re-iterate my support
for byte counting. It's the Right Thing To Do, and theoretical backwards
compatibility with existing non-standard non-widely-deployed syslog over
TCP solutions isn't a good enough reason to put bad ideas in the standard.
Hi,
Here is my review of the protocol-17 document.
Let me apologize (slightly) for such a thorough review, late in the
process, but as co-chair I need to say I reviewed this thoroughly and
that I agree it is ready to be published as a standard. I am much
pickier about a document I will sign-off
