[Syslog] AD review discuss/comments for draft-ietf-syslog-dtls - NULL
"t.petch" <ietfc@btconnect.com> Tue, 25 May 2010 13:26 UTC
Return-Path: <ietfc@btconnect.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 4190D3A70D2 for <syslog@core3.amsl.com>; Tue, 25 May 2010 06:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[AWL=-0.505, BAYES_50=0.001]
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 tZwD1KB3r+t2 for <syslog@core3.amsl.com>; Tue, 25 May 2010 06:26:55 -0700 (PDT)
Received: from c2beaomr03.btconnect.com (c2beaomr03.btconnect.com [213.123.26.181]) by core3.amsl.com (Postfix) with ESMTP id 0905D3A70F6 for <syslog@ietf.org>; Tue, 25 May 2010 06:26:54 -0700 (PDT)
Received: from pc6 (host86-172-78-59.range86-172.btcentralplus.com [86.172.78.59]) by c2beaomr03.btconnect.com with SMTP id LZE20177; Tue, 25 May 2010 14:26:38 +0100 (BST)
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=0001.0A0B0301.4BFBD00D.03B0, actions=tag
Message-ID: <017101cafc05$1a752000$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "t.petch" <ietfc@btconnect.com>, turners@ieca.com
References: <20100511182040.16429@web6.nyc1.bluetie.com><01c701caf904$d1662c40$4001a8c0@gateway.2wire.net>, <4BF7F544.70004@ieca.com><808FD6E27AD4884E94820BC333B2DB775BC0E09522@NOK-EUMSG-01.mgdnok.nokia.com> <000b01cafbed$37c29380$4001a8c0@gateway.2wire.net>
Date: Tue, 25 May 2010 14:19:17 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Junkmail-Status: score=10/50, host=c2beaomr03.btconnect.com
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0207.4BFBD010.0027, ss=1, fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine
X-Junkmail-IWF: false
Cc: syslog@ietf.org
Subject: [Syslog] AD review discuss/comments for draft-ietf-syslog-dtls - NULL
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: Tue, 25 May 2010 13:26:56 -0000
Another outstanding issue is the question of NULL options in the ciphersuites with Tim Polk suggesting something along the lines of OLD: Implementations MUST support DTLS 1.1 [RFC4347] and MUST support the mandatory to implement cipher suite, which is TLS_RSA_WITH_AES_128_CBC_SHA. NEW: Implementations MUST support DTLS 1.1 [RFC4347] and MUST at a minimum support the mandatory to implement cipher suite, which is TLS_RSA_WITH_AES_128_CBC_SHA. If additional cipher suites are supported, then implementations MUST NOT negotiate a cipher suite that employs NULL encryption, integrity, or authentication algorithms. The justification is that "disclosure is one of the primary threats described in Section 4," I disagree. The threat of disclosure comes from RFC5425 s2 "Some data in syslog messages is sensitive and may be useful to an attacker, such as the password of an authorized administrator or user." but the fact that someone, somewhere may put a password in a syslog message I do not see as grounds for requiring everyone else in the world to encrypt everything. Encryption is a pain, it costs, and we should not require it unless it can be justified; these are remote, low-powered network boxes we are talking about, not enterprise servers. So while I agree we should require authentication, I see no justification for encryption. In passing, there was a request for a reference for the ciphersuite, which could be covered by adding 'as specified there' after 'cipher suite'. Tom Petch
- [Syslog] AD review comments for draft-ietf-syslog… Sean Turner
- Re: [Syslog] AD review comments for draft-ietf-sy… Chris Lonvick
- Re: [Syslog] AD review comments for draft-ietf-sy… Joseph Salowey (jsalowey)
- Re: [Syslog] AD review comments for draft-ietf-sy… Sean Turner
- Re: [Syslog] AD review comments for draft-ietf-sy… Joseph Salowey (jsalowey)
- Re: [Syslog] AD review comments for draft-ietf-sy… tom.petch
- Re: [Syslog] AD review comments for draft-ietf-sy… Chris Lonvick
- Re: [Syslog] AD review comments for draft-ietf-sy… Sean Turner
- Re: [Syslog] AD review comments for draft-ietf-sy… Tim Evens
- Re: [Syslog] AD review comments for draft-ietf-sy… tom.petch
- Re: [Syslog] AD review comments for draft-ietf-sy… Tim Evens
- [Syslog] AD review discuss/comments for draft-iet… t.petch
- Re: [Syslog] AD review discuss/comments for draft… Rainer Gerhards
- Re: [Syslog] AD review discuss/comments for draft… Sean Turner
- Re: [Syslog] AD review discuss/comments for draft… Pasi.Eronen
- Re: [Syslog] AD review discuss/comments for draft… robert.horn
- Re: [Syslog] AD review discuss/comments for draft… t.petch
- Re: [Syslog] AD review discuss/comments for draft… t.petch
- Re: [Syslog] AD review discuss/comments for draft… Pasi.Eronen
- [Syslog] AD review discuss/comments for draft-iet… t.petch