IETF Logo Mail Archive

Re: [Syslog] RE: byte-counting vs special character

Carson Gaspar <carson@taltos.org> Wed, 16 August 2006 19:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDR6H-0007do-J1; Wed, 16 Aug 2006 15:30:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDR6F-0007de-R7 for syslog@ietf.org; Wed, 16 Aug 2006 15:30:47 -0400
Received: from dsl081-242-052.sfo1.dsl.speakeasy.net ([64.81.242.52] helo=gandalf.taltos.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDR6E-0003JX-FR for syslog@ietf.org; Wed, 16 Aug 2006 15:30:47 -0400
Received: from gandalf.taltos.org (localhost [127.0.0.1]) by gandalf.taltos.org (Postfix) with ESMTP id 31C5D21CD3 for <syslog@ietf.org>; Wed, 16 Aug 2006 12:30:45 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on gandalf.taltos.org
X-Spam-Level:
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0
Received: from [192.168.1.2] (unknown [192.168.1.2]) by gandalf.taltos.org (Postfix) with ESMTP id 2405621CD2 for <syslog@ietf.org>; Wed, 16 Aug 2006 12:30:45 -0700 (PDT)
Date: Wed, 16 Aug 2006 12:32:46 -0700
From: Carson Gaspar <carson@taltos.org>
To: syslog@ietf.org
Subject: Re: [Syslog] RE: byte-counting vs special character
Message-ID: <3EC76EAEC1590ED5FF81F03E@[192.168.1.2]>
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA174DFB@grfint2.intern.adiscon.com>
References: <577465F99B41C842AAFBE9ED71E70ABA174DFB@grfint2.intern.adiscon.c om>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc:
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog@lists.ietf.org>
List-Help: <mailto:syslog-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=subscribe>
Errors-To: syslog-bounces@lists.ietf.org

Escaping precludes no-configuration backwards compatibility, as no legacy 
syslog-over-tcp code does escaping. So if you want to interoperate with 
existing code, you must have a "don't escape or expect escapes" switch in 
your code. If you're going to do that, just have a "LF mode vs byte-count 
mode" switch. This whole backwards compat argument is bogus, iff we decide 
to escape embedded LF instead of forbidding it. And I have yet to see 
anyone argue for LF on any grounds except backwards compatibility.

-- 
Carson

_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog

v2.30.2 | Report a Bug | By Email | System Status