Re: [Syslog] New Version: draft-ietf-syslog-dtls-02
Chris Lonvick <clonvick@cisco.com> Mon, 08 March 2010 18:49 UTC
Return-Path: <clonvick@cisco.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 85D0B3A6B1A for <syslog@core3.amsl.com>; Mon, 8 Mar 2010 10:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level:
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 wldqrX0ZYmbr for <syslog@core3.amsl.com>; Mon, 8 Mar 2010 10:49:47 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id C2C493A69D5 for <syslog@ietf.org>; Mon, 8 Mar 2010 10:49:47 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.49,603,1262563200"; d="scan'208";a="162471386"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 08 Mar 2010 18:49:52 +0000
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.16.68]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o28InpWc015358; Mon, 8 Mar 2010 18:49:51 GMT
Date: Mon, 08 Mar 2010 10:49:51 -0800
From: Chris Lonvick <clonvick@cisco.com>
To: Richard Graveman <rfgraveman@gmail.com>
In-Reply-To: <45c8c21a1003051621w5f851e3q7fcb93af0050d8d8@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.1003080912480.21786@sjc-cde-011.cisco.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE509C5B555@xmb-sjc-225.amer.cisco.com> <Pine.GSO.4.63.1003051448070.17566@sjc-cde-011.cisco.com> <45c8c21a1003051621w5f851e3q7fcb93af0050d8d8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; boundary="-559023410-838545539-1268069503=:21786"
Content-ID: <Pine.GSO.4.63.1003081046200.21786@sjc-cde-011.cisco.com>
Cc: syslog@ietf.org
Subject: Re: [Syslog] New Version: draft-ietf-syslog-dtls-02
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: Mon, 08 Mar 2010 18:49:48 -0000
Hi Rich, I appreciate the review. RFC 4279 also says: ===== The ciphersuites defined in this document are intended for a rather limited set of applications, usually involving only a very small number of clients and servers. Even in such environments, other alternatives may be more appropriate. If the main goal is to avoid Public-Key Infrastructures (PKIs), another possibility worth considering is using self-signed certificates with public key fingerprints. Instead of manually configuring a shared secret in, for instance, some configuration file, a fingerprint (hash) of the other party's public key (or certificate) could be placed there instead. ===== This is why we have the parts in there about "MUST be able to generate a self-signed cert" (identical language to RFC 5425), and the use of fingerprints (reference back to 5425). I understand what you're saying about SHA-1, however I don't think that will be an issue since the signature on the certificate is not even verified if you use fingerprints. I'll also back up and say that I havn't seen the IESG give specific guidance about not using SHA-1. Thanks, Chris On Fri, 5 Mar 2010, Richard Graveman wrote: >> I've looked over these changes and feel that they address the WGLC comments >> that were received. I'd appreciate it if the people who did the reviews >> would also do a check. > > Requiring certificates is a lot of extra baggage for worsened > security. All the commonly encountered certificates today are based on > signatures of weak hash functions, primarily SHA-1. Cipher suites > like: > > 0x00,0xA8 TLS_PSK_WITH_AES_128_GCM_SHA256 [RFC5487] > 0x00,0xA9 TLS_PSK_WITH_AES_256_GCM_SHA384 [RFC5487] > > do not suffer from the twin disease of weak and inefficient security > and ought to be an option, as Tschonfig and Eronen say in 4279: > > ... pre-shared keys may be more convenient from a key > management point of view. For instance, in closed environments > where the connections are mostly configured manually in advance, > it may be easier to configure a PSK than to use certificates. > Another case is when the parties already have a mechanism for > setting up a shared secret key, and that mechanism could be used > to "bootstrap" a key for authenticating a TLS connection. > > This is precisely the environment is which I would expect to find a > lot of syslog, as opposed to "TLS on the Web." > > Rich Graveman >
- [Syslog] New Version: draft-ietf-syslog-dtls-02 Joseph Salowey (jsalowey)
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Chris Lonvick
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Richard Graveman
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Richard Graveman
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Juergen Schoenwaelder
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Joseph Salowey (jsalowey)
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Richard Graveman
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Joseph Salowey (jsalowey)
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Chris Lonvick
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Richard Graveman
- Re: [Syslog] New Version: draft-ietf-syslog-dtls-… Chris Lonvick