Re: [Syslog] Small draft for Syslog File Storage?

Anton Chuvakin <anton@chuvakin.org> Thu, 11 November 2010 18:48 UTC

Return-Path: <anton.chuvakin@gmail.com>
X-Original-To: syslog@core3.amsl.com
Delivered-To: syslog@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3CC13A6950 for <syslog@core3.amsl.com>; Thu, 11 Nov 2010 10:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5jyqTAsMnAT for <syslog@core3.amsl.com>; Thu, 11 Nov 2010 10:48:47 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id AB2E13A67E6 for <syslog@ietf.org>; Thu, 11 Nov 2010 10:48:46 -0800 (PST)
Received: by wwb34 with SMTP id 34so181179wwb.13 for <syslog@ietf.org>; Thu, 11 Nov 2010 10:49:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=eW1vF9kV51GKodymjJGWzUANcgIyuqwHdryImASf7jk=; b=u+Ui7IbRqLEIxGwQeaqzhfCR0x4yyRBE7weh4MTDPMzPt8uuyvycP6Xss91YOV17Bd fE+McCueueIZCG1ALGkQOPGcTQrOH0uQPbhSSsUT7/AkFeAY34JZW6Ux05sfXIAf60ur hUzeX5zSsVJi2U24bJhAy/QSfyLdzlVNP9SUA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=uVrbscB2Jdb2c4ehPmzuG2flobed12XIJI/SbFEcnYVoYl96tWIq9QiZeLYFrTRlG6 4UZ+3w22b2DC8HQLyzK/unA0KKdMow5du10TAG5eM/0MFVQShpNkcm+xDaqOch+dLeVB UZYYo7Ld+eTVP+Mlrr+rL61jjBRtZnGliu6CE=
Received: by 10.227.63.7 with SMTP id z7mr1280660wbh.21.1289501355626; Thu, 11 Nov 2010 10:49:15 -0800 (PST)
MIME-Version: 1.0
Sender: anton.chuvakin@gmail.com
Received: by 10.227.136.17 with HTTP; Thu, 11 Nov 2010 10:48:45 -0800 (PST)
In-Reply-To: <9B6E2A8877C38245BFB15CC491A11DA71DD6C5@GRFEXC.intern.adiscon.com>
References: <9B6E2A8877C38245BFB15CC491A11DA71DD6C5@GRFEXC.intern.adiscon.com>
From: Anton Chuvakin <anton@chuvakin.org>
Date: Thu, 11 Nov 2010 10:48:45 -0800
X-Google-Sender-Auth: qR2Ehh2_nr1ysvvitgSkxXBXHLI
Message-ID: <AANLkTi=S6K-A-ciGuSYHMhQQy+Tv=+N+H2dhJxaRPLiK@mail.gmail.com>
To: syslog@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Syslog] Small draft for Syslog File Storage?
X-BeenThere: syslog@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/syslog>
List-Post: <mailto:syslog@ietf.org>
List-Help: <mailto:syslog-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2010 18:50:36 -0000

> In what we did, we specified the on-the-wire format. However, we did not
> specify any format to use when persisting syslog data to a file.

How big of a deal is this, really? Now, I don't question that
consistent representation is alway better (whether stored or flying
over the wire),  but that does not seem like a 'top syslog problem'
kinda issue to me.

Storage consistency might be way down on the list of issues that will
make syslog more useful for producers/consumers of the data - while
still allow the changes to be adopted....

-- 
Dr. Anton Chuvakin
Site: http://www.chuvakin.org
Blog: http://www.securitywarrior.org
LinkedIn: http://www.linkedin.com/in/chuvakin
Consulting: http://www.securitywarriorconsulting.com
Twitter: @anton_chuvakin
Google Voice: +1-510-771-7106