Re: [TLS] I-D Action: draft-ietf-tls-negotiated-ff-dhe-00.txt
Peter Gutmann <pgut001@cs.auckland.ac.nz> Thu, 24 July 2014 14:53 UTC
Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9B91A03D6 for <tls@ietfa.amsl.com>; Thu, 24 Jul 2014 07:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KcH7-0WmH1lv for <tls@ietfa.amsl.com>; Thu, 24 Jul 2014 07:53:52 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28ACE1A03C2 for <tls@ietf.org>; Thu, 24 Jul 2014 07:53:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1406213632; x=1437749632; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=M8iyxcjjZItqyG7cgq8m6s5n/21KNJ0odB1GGxW3hT0=; b=fw5gMAaB6JRSBwou5vjXNoWxZKcYm6e4T0FCgrXP8rR3kQAw8msqre3s keDEef+LSXeR6Rc+Nf5JwLwv9to24zcwSdRRUBhdSwJN0S3rvJgbxET2T oPUv1VC32m4huvT9XQZrtDz9fxrvQej1XJX6ZGP2dGjdfUetyqnEORR3A k=;
X-IronPort-AV: E=Sophos;i="5.01,724,1399982400"; d="scan'208";a="265551589"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.171 - Outgoing - Outgoing
Received: from uxchange10-fe4.uoa.auckland.ac.nz ([130.216.4.171]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 25 Jul 2014 02:53:47 +1200
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.247]) by uxchange10-fe4.UoA.auckland.ac.nz ([169.254.109.63]) with mapi id 14.03.0174.001; Fri, 25 Jul 2014 02:53:46 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: [TLS] I-D Action: draft-ietf-tls-negotiated-ff-dhe-00.txt
Thread-Index: Ac+nTxIDPv2cUlFtTNOADpXqJ0CiGQ==
Date: Thu, 24 Jul 2014 14:53:46 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C738EFB003E@uxcn10-5.UoA.auckland.ac.nz>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/n8zyEyO7YMRSQktu3I6ONEVGV2E
Subject: Re: [TLS] I-D Action: draft-ietf-tls-negotiated-ff-dhe-00.txt
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jul 2014 14:53:59 -0000
<internet-drafts@ietf.org> writes: > Traditional finite-field-based Diffie-Hellman (DH) key exchange > during the TLS handshake suffers from a number of security, > interoperability, and efficiency shortcomings. These shortcomings > arise from lack of clarity about which DH group parameters TLS > servers should offer and clients should accept. This document offers > a solution to these shortcomings for compatible peers by establishing > a registry of DH parameters with known structure and a mechanism for > peers to indicate support for these groups. Some comments: - Why not just use the well-known and -accepted IKE groups from RFC 3526 for this? In fact why invent entirely new groups (that don't even cover the existing range in RFC 3526) when there's already well-established ones available? - What's the thinking behind a 2432-bit group? 2048-bit I could understand, 2560 bits perhaps, but 2432? - Publishing the values of q (rather than just telling people how to calculate them) would be good, since it'd provide known-correct values for them. In general though, we don't need yet another set of parameters, all that's needed is a mechanism for specifying the existing RFC 3526 groups. Peter.
- [TLS] I-D Action: draft-ietf-tls-negotiated-ff-dh… internet-drafts
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Peter Gutmann
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Yoav Nir
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Andrey Jivsov
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Peter Gutmann
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Watson Ladd
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Daniel Kahn Gillmor
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Yaron Sheffer
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Peter Gutmann
- Re: [TLS] I-D Action: draft-ietf-tls-negotiated-f… Fedor Brunner