Re: [TLS] confirming the room’s consensus: adopt HKDF PRF for TLS 1.3

Nikos Mavrogiannopoulos <nmav@redhat.com> Wed, 01 April 2015 18:53 UTC

Return-Path: <nmavrogi@redhat.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 CCB181A8881 for <tls@ietfa.amsl.com>; Wed, 1 Apr 2015 11:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level:
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OcvucdgeSWG9 for <tls@ietfa.amsl.com>; Wed, 1 Apr 2015 11:53:12 -0700 (PDT)
Received: from mx5-phx2.redhat.com (mx5-phx2.redhat.com [209.132.183.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4E211A886B for <tls@ietf.org>; Wed, 1 Apr 2015 11:53:09 -0700 (PDT)
Received: from zmail22.collab.prod.int.phx2.redhat.com (zmail22.collab.prod.int.phx2.redhat.com [10.5.83.26]) by mx5-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t31Ir7O9059803; Wed, 1 Apr 2015 14:53:07 -0400
Date: Wed, 1 Apr 2015 14:53:07 -0400 (EDT)
From: Nikos Mavrogiannopoulos <nmav@redhat.com>
To: Sean Turner <turners@ieca.com>
Message-ID: <1082369316.6361228.1427914387267.JavaMail.zimbra@redhat.com>
In-Reply-To: <4A5C6D8F-6A28-4374-AF1F-3B202738FB1D@ieca.com>
References: <4A5C6D8F-6A28-4374-AF1F-3B202738FB1D@ieca.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [94.112.138.148, 10.5.101.182]
X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF31 (Linux)/8.0.6_GA_5922)
Thread-Topic: confirming the =?utf-8?B?cm9vbeKAmXM=?= consensus: adopt HKDF PRF for TLS 1.3
Thread-Index: T4JENAzDlqDpBcUXUQEtkSX7gFLrZA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/8ajKbylIoLr-_yb_BFyUtViuruU>
Cc: tls <tls@ietf.org>
Subject: Re: [TLS] =?utf-8?q?confirming_the_room=E2=80=99s_consensus=3A_adopt_?= =?utf-8?q?HKDF_PRF_for_TLS_1=2E3?=
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: Wed, 01 Apr 2015 18:53:19 -0000

----- Original Message -----
> This message is to confirm the consensus reached @ the IETF 92 TLS session in
> Dallas and at the TLS Interim in Seattle to make the TLS 1.3 PRF be an
> HKDF-based PRF (see
> http://datatracker.ietf.org/doc/rfc5869/?include_text=1).
> Please indicate whether or not you agree with the consensus by 2015-04-17.
> If not, please indicate why.  Also, please note that we’re interested in
> uncovering new issues not rehashing issues already discussed.

I believe the question is totally unwarranteed. No-one has presented any argument
on why the TLS PRF is not sufficient for its purpose. The only arguments presented
are theoretical advantages of HKDF, which are fine, but do they add value to TLS?
Does the advantages of HKDF translate into weaknesses of the TLS PRF?

So no matter the output of that poll the result will be an uneducated guess. In all cases
it is alarming to see the easiness with which the protocol is being rewritten completely.
Now its only similarity with TLS 1.2 is the TLS acronym. Would that rewrite bring value
in par with the efford needed for the rewrite? Would it make us safer in 2030 or are we
simply apply yesterday's technology today?

regards,
Nikos