Re: [TLS] Exporter output size

Eric Rescorla <ekr@rtfm.com> Wed, 05 October 2016 03:49 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC9F128874 for <tls@ietfa.amsl.com>; Tue, 4 Oct 2016 20:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 ziG0tPpW5EJb for <tls@ietfa.amsl.com>; Tue, 4 Oct 2016 20:49:40 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DCD3129492 for <tls@ietf.org>; Tue, 4 Oct 2016 20:49:39 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id e20so48440ybb.0 for <tls@ietf.org>; Tue, 04 Oct 2016 20:49:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vPYmlh6xrGREq8+4XNCrKbaYwKP3dgHOzg7CLDi436A=; b=ZfpFq2PnVL779byfpr/hado9wAZbUY14nR0iMhw4ppLq5yIO07tKeYpcm0+p2fpEb7 9tPnfSw2Muixih6fC9zU7QjHOudkT3TH2AxbqY+3dr83Iwh0nkHv0aL13Z5kdLZhoL/o gG0yr05yc1p8LE0pDgZVGffGhbRAPghLtduvf/bBCqZLDrYOgc/dM4obSo+LTE8Dminb lhVziEF742I3+Vp5CuEfPWWiKKfnKL8SYJOHrJ6n2yMnEZ95+TCm1me8Uy1CGKVQOMEE yY+CiL7zJB+bJY9D20vXmyDGvwc0xD5wEuWcZfgBWag6qavS6g2X4Xeyp9vIXRe9Peg2 myvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vPYmlh6xrGREq8+4XNCrKbaYwKP3dgHOzg7CLDi436A=; b=gip6KTHGZLXr2IGbWhjxAJLDb+RLQRtZu6A/iqzj8O7TqUJUtsgz5INutCs2ZDDi40 /pb8gDPeCOvEIRLFpw2RQ8k2u/Z0tcwzR3Qa5+oHu9upazobDSuQUn5HtUjQsYPGyH7Q a+r3Ep4kb3jSvtUvENJn+su1EVkeH4P/itL3w5r39TTwMs8PLOfbefoOP7sEHRtOr9FH wpuwdjaIeIwmYWjf/MRU7gg7eq57uJnJd8HMjz2K55kwxKUtOpW+kEp74JSQEhEVtOOC rJI/V9T2vp61FKmAI+OfhttoI1ZNdo/6THZSHfjenpjTU/pjxQwP1f17l32GCXJjwFKT 2bWQ==
X-Gm-Message-State: AA6/9Rli1GtkgPN8BO5mGEeLepHPejXFT4JIWIVe43gG4pduS7aq6XT9XNcuCYhCOl0TC09E5Tcid/SYrOFIiA==
X-Received: by 10.37.3.132 with SMTP id 126mr5380331ybd.64.1475639378484; Tue, 04 Oct 2016 20:49:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.160.10 with HTTP; Tue, 4 Oct 2016 20:48:58 -0700 (PDT)
In-Reply-To: <CABkgnnVc2uegQX1zdFamBtkDfzw9k3aBx6xFbNH4PpgWScALew@mail.gmail.com>
References: <CABkgnnVc2uegQX1zdFamBtkDfzw9k3aBx6xFbNH4PpgWScALew@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 4 Oct 2016 20:48:58 -0700
Message-ID: <CABcZeBMLbDv2oOu-GFdmm2cYNbNsrocnZ5KdW4D5HBbXdAEK1g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c06d52f8f7ff053e1610b4
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/71OoP4gH_NdNDQKmMPayfVZLUWI>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Exporter output size
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Oct 2016 03:49:41 -0000

On Tue, Oct 4, 2016 at 6:32 PM, Martin Thomson <martin.thomson@gmail.com>;
wrote:

> After a bunch of discussion about the consequences of having
> insufficient output from various stages of the hash functions... Could
> we make an amendment to TLS 1.3 to force the output size of the
> exporter to be the size of the underlying hash output?  That is,
> remove the length parameter.  Or is a change to the API too
> disruptive?
>

I don't think this is a good idea. There are plenty of reasons why you
would want to
export values != hash_len (e.g., cryptographic keys). Putting a restriction
here just
pushes the problem around

-Ekr


> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>