Re: [Syslog] transport-tls vs. syslog-sign

robert.horn@agfa.com Fri, 16 May 2008 15:16 UTC

Return-Path: <syslog-bounces@ietf.org>
X-Original-To: syslog-archive@megatron.ietf.org
Delivered-To: ietfarch-syslog-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9E8D28C203; Fri, 16 May 2008 08:16:55 -0700 (PDT)
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 223BA28C203; Fri, 16 May 2008 08:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 K7Xs0tRW+79Q; Fri, 16 May 2008 08:16:53 -0700 (PDT)
Received: from mornm01-out.agfa.com (mornm01-out.agfa.com [134.54.1.75]) by core3.amsl.com (Postfix) with ESMTP id 6CB7D28C1FD; Fri, 16 May 2008 08:16:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,498,1204498800"; d="scan'208";a="45710897"
Received: from morswa037.agfa.be (HELO morswa037.be.local) ([10.232.220.21]) by mornm01-out.agfa.com with ESMTP; 16 May 2008 17:16:06 +0200
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA30902C@grfint2.intern.adiscon.com>
To: rgerhards@hq.adiscon.com
MIME-Version: 1.0
Message-ID: <OF6926C10B.03BAC96D-ON8525744B.005371C5-8525744B.0053DDFB@agfa.com>
From: robert.horn@agfa.com
Date: Fri, 16 May 2008 11:16:02 -0400
Cc: syslog@ietf.org, syslog-bounces@ietf.org
Subject: Re: [Syslog] transport-tls vs. syslog-sign
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: syslog-bounces@ietf.org
Errors-To: syslog-bounces@ietf.org

"Rainer Gerhards" <rgerhards@hq.adiscon.com> wrote on 05/16/2008 11:06:45 
AM:


> 
> [Rainer]
> The differences I see is that between the two there are differences in
> what modes can be used. For example
> 
>                  -sign     -transport-tls
> x.509            yes        yes
> fingerprints     no         yes
> openPgP          yes        no
> (other)          yes        (N/A)
> 
> Also, -sign specifies how certificates are distributed (section 5.2, 5.3
> among others). -transport-tls does not talk about certificate
> distribution. In fact, -sign focuses very much on the distribution. 
> 

...
> 
> As I outlined in my mail yesterday, -tls cannot really authenticate the
> originator. -sign can do that. -sign cannot provide confidentiality.
> -tls can do that. So a really secure system would need to utilize both.
> Then, it would at least be useful to have the same set of drafts reuse
> some ideas. Even the relationship between those two is not spelled
> out...

I make this distinction on authentication.  -tls authenticates the sender 
of the message.  -sign authenticates the contents and creator of the 
message.  Both have their uses, and they are independent concepts.  I find 
in practice that for syslog style operation I am usually satisfied with 
-tls plus the knowledge that the sender has done whatever is appropriate 
to ensure that message contents are appropriate.  But, there are other 
syslog situations where that is not a reasonable assumption, and -sign is 
then needed.

R Horn
_______________________________________________
Syslog mailing list
Syslog@ietf.org
https://www.ietf.org/mailman/listinfo/syslog