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

"Rainer Gerhards" <rgerhards@hq.adiscon.com> Thu, 17 August 2006 02:42 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDXpY-0007pI-3u; Wed, 16 Aug 2006 22:42:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDXpW-0007pD-Uc for syslog@ietf.org; Wed, 16 Aug 2006 22:41:58 -0400
Received: from mail.hq.adiscon.com ([84.245.151.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDXpV-0007Ds-KC for syslog@ietf.org; Wed, 16 Aug 2006 22:41:58 -0400
Received: from localhost (localhost [127.0.0.1]) by mail.hq.adiscon.com (Postfix) with ESMTP id 973D49C00C; Thu, 17 Aug 2006 04:43:29 +0200 (CEST)
Received: from mail.hq.adiscon.com ([127.0.0.1]) by localhost (mail.grf.adiscon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19328-02; Thu, 17 Aug 2006 04:43:24 +0200 (CEST)
Received: from grfint2.intern.adiscon.com (grfint2 [172.19.0.6]) by mail.hq.adiscon.com (Postfix) with ESMTP id C18A99C00B; Thu, 17 Aug 2006 04:43:24 +0200 (CEST)
Subject: RE: [Syslog] RE: byte-counting vs special character
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Aug 2006 04:41:49 +0200
Content-class: urn:content-classes:message
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA174E05@grfint2.intern.adiscon.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-Reply-To: <2B15665BA66B721F16F22A56@[192.168.1.2]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Syslog] RE: byte-counting vs special character
Thread-Index: AcbBoATsieQeRsYBTmyuyYA/T3xm/AABofkg
From: Rainer Gerhards <rgerhards@hq.adiscon.com>
To: Carson Gaspar <carson@taltos.org>, syslog@ietf.org
X-Virus-Scanned: by amavisd-new-2.3.3 (20050822) (Debian) at adiscon.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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

 

> -----Original Message-----
> From: Carson Gaspar [mailto:carson@taltos.org] 
> Sent: Wednesday, August 16, 2006 7:55 PM
> To: syslog@ietf.org
> Subject: RE: [Syslog] RE: byte-counting vs special character
> 
> --On Thursday, August 17, 2006 3:18 AM +0200 Rainer Gerhards 
> <rgerhards@hq.adiscon.com> wrote:
> 
> > Caspar - since when does legacy code do escaping? (Even if I've
> > overlooked it, we might use a different escape character...)
> 
> It doesn't. However, if the escape character is legal in 
> legacy code, it 
> can appear twice. Which will be converted to a single escape 
> character by a 
> new receiver. Which is a bug. Which is why I said:


No - a new receiver checks the version field and detects that it is a
legacy message. This is what the header is designed for. As it knows it
is legacy, it won't unescape...

Rainer 

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