Re: [TLS] Do we need DH?
Nico Williams <nico@cryptonector.com> Fri, 02 January 2015 17:17 UTC
Return-Path: <nico@cryptonector.com>
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 97C251A1B84 for <tls@ietfa.amsl.com>; Fri, 2 Jan 2015 09:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 FwPU8HHGDcNh for <tls@ietfa.amsl.com>; Fri, 2 Jan 2015 09:17:16 -0800 (PST)
Received: from homiemail-a86.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 74A981A1B55 for <tls@ietf.org>; Fri, 2 Jan 2015 09:17:16 -0800 (PST)
Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id 5544336006D; Fri, 2 Jan 2015 09:17:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=hE9NhI8rDVDIlB JuZy+aKF3arQI=; b=gFUJDMG1pSqLVejqB5vKsjji4VrGZOBe24Rlr2BpiYyQOS VUBqq/BqrXN5ThQUwtU30O2k3lYnFIPScB15KfCJO/00hWlwshUuhvFiKOL4ja21 29Gnj8B5a7PxKaF7o/Sg4c1PnUqabFVPChXQKp1hJmjHHq7eHRB0IxPf1p4Z0=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPA id 00E4F36006B; Fri, 2 Jan 2015 09:17:15 -0800 (PST)
Date: Fri, 02 Jan 2015 11:17:15 -0600
From: Nico Williams <nico@cryptonector.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Message-ID: <20150102171711.GY24442@localhost>
References: <CACsn0cmD=YA4i889f--e_b-OahUVoYdKyQUaiUN--QKOmqn8uA@mail.gmail.com> <54A252EA.1010905@iki.fi> <2348107.Lj21YcAO1u@pintsize.usersys.redhat.com> <DF638EB0-A163-4DBD-B095-43EEDA4D9DB1@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DF638EB0-A163-4DBD-B095-43EEDA4D9DB1@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/dg_1_WB6QGJyvDznISAHdSx8624
Cc: tls@ietf.org
Subject: Re: [TLS] Do we need DH?
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: Fri, 02 Jan 2015 17:17:17 -0000
On Fri, Jan 02, 2015 at 03:08:07PM +0200, Yoav Nir wrote: > > On Jan 2, 2015, at 2:46 PM, Hubert Kario <hkario@redhat.com> wrote: > > On Tuesday 30 December 2014 09:23:22 Tapio Sokura wrote: > >> With regards to all eggs being in the same basket, AES is also something > >> that really should have a realistic alternative standardized and > >> deployed _before_ (/if) AES is broken. Like SHA-3 is coming around the > >> corner while SHA-2 is still well alive and kicking. > > > > We do have Camellia ciphers defined, PFS AEAD included (RFC 6367). > > That, and the ChaCha20+Poly1305 AEAD will be defined when http://tools.ietf.org/html/draft-mavrogiannopoulos-chacha-tls-04 is adopted. I think Hubert may be referring to the need for for interoperable alternatives. As in: being likely to find those alternatives deployed. IOW, we need at least two realistic *REQUIRED to implement* algorithms (curves for ECC) of most kinds: two hash functions, two PRFs, two ECDH curves, two digital signature algorithms (e.g., RSA and E*DSA), two AEAD ciphers. For some kinds of algorithms (ciphers) this might be difficult, politically. But it's worth considering. Nico --
- Re: [TLS] Do we need DH? Fedor Brunner
- Re: [TLS] Do we need DH? Tapio Sokura
- [TLS] Do we need DH? Watson Ladd
- Re: [TLS] Do we need DH? Alyssa Rowan
- Re: [TLS] Do we need DH? Yoav Nir
- Re: [TLS] Do we need DH? Peter Gutmann
- Re: [TLS] Do we need DH? Brian Smith
- Re: [TLS] Do we need DH? Maarten Bodewes
- Re: [TLS] Do we need DH? Hubert Kario
- Re: [TLS] Do we need DH? Yoav Nir
- Re: [TLS] Do we need DH? Alyssa Rowan
- Re: [TLS] Do we need DH? Nico Williams
- Re: [TLS] Do we need DH? Yoav Nir
- Re: [TLS] Do we need DH? Florian Weimer
- [TLS] Spec tls13 comments, handshake tampering, m… Michael Clark
- Re: [TLS] Spec tls13 comments, handshake tamperin… Michael Clark
- Re: [TLS] Spec tls13 comments, handshake tamperin… Nikos Mavrogiannopoulos