Re: [TLS] Would there be security issues with a 0-RTT resume?

Bill Cox <waywardgeek@google.com> Sun, 06 December 2015 03:32 UTC

Return-Path: <waywardgeek@google.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 67EA41B2A0D for <tls@ietfa.amsl.com>; Sat, 5 Dec 2015 19:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 miU63mSHSPTS for <tls@ietfa.amsl.com>; Sat, 5 Dec 2015 19:32:37 -0800 (PST)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 7572A1B29F6 for <TLS@ietf.org>; Sat, 5 Dec 2015 19:32:37 -0800 (PST)
Received: by iouu10 with SMTP id u10so155195984iou.0 for <TLS@ietf.org>; Sat, 05 Dec 2015 19:32:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=94nN872xf1RAdDelzuBvXMF/6grvoyBikQ64CCYP+hw=; b=PSM5iYMt1vybMmuipOsCqGzs6sZeJiLzJmqux3NKzuAEUfo0TlgUVOkIj5CqMb6Tq+ XrrzkuPjyBcG/Z7+RIaf63d14snaU+oZr6t437WZSSA/SFiJ77yVXvOS+T/yWbZmX+/a AO16QJqAj75PpXiPC6iZ559hB83dI2FBT2SrySFJ/rpfmoVFt5ji5Ev7Mq4G2XDENQov HQQoAqN7GrUWlMi85QHPaSC8Iyr/n1BYLycq78uXr+2AmohDh3AqzWAY3TMEQ7w+shuy VghncOPv80jwwdGQStmkZvP3B2kgPORgURc1X+eI6cUTXMNTT+B2QDkZEEYYH54Ec0LO N9EA==
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:date :message-id:subject:from:to:cc:content-type; bh=94nN872xf1RAdDelzuBvXMF/6grvoyBikQ64CCYP+hw=; b=dwxqKicLd97Z5aYZkE3yI0wNhPtvOIaSGh4Muc1hcAc8mU+nH9kuFJRdoS+XiPA3Vv +0WTWv5G5mSlMPh568aLpwG3L+GTOHP2Fm7pE5MAX5snXOUl+1f8mfpVieYP8GEApj2N yjT4MIfMYXhv2JBe7yg9hIO1w6NBl7aK0OWDrh0x6gaGLIY+utBN/FA4C7EyypZCiidc LwwKRWkmielGAP8r3XEiylPVUZGsx/uXfiR0UTHeKAEMigykLCXASujRAgxolx4zuFo9 61/cVBlaalei6SoAuypL8/kqSXDkg3MvoJhTRim/00CTZ0XadLiv9VK0zTVs/PGuq2m5 KLbA==
X-Gm-Message-State: ALoCoQkx/CqcJNifjEvvxCNjhfA+7gdHJJil4aN8E1OwM92jruIz9cbe/yzKJc4VDL74EO2O7TLR
MIME-Version: 1.0
X-Received: by 10.107.152.133 with SMTP id a127mr21389174ioe.60.1449372756783; Sat, 05 Dec 2015 19:32:36 -0800 (PST)
Received: by 10.107.173.15 with HTTP; Sat, 5 Dec 2015 19:32:36 -0800 (PST)
In-Reply-To: <CABcZeBOujQ2Q5NoCOuQ3skyqDDs72-=P07k1WTZSDgMJWti+gQ@mail.gmail.com>
References: <CAH9QtQHtiuKnYoYoDpiNVz31HZH23sv9Bt-Rya985tWHorhcYA@mail.gmail.com> <CABcZeBOujQ2Q5NoCOuQ3skyqDDs72-=P07k1WTZSDgMJWti+gQ@mail.gmail.com>
Date: Sat, 5 Dec 2015 19:32:36 -0800
Message-ID: <CAH9QtQEy4abNv5SeWJL55f0DAkPA7eQdOw8Rz4XEaY9WXnn3uA@mail.gmail.com>
From: Bill Cox <waywardgeek@google.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=001a1140e69e50ff3d0526326441
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/Knbd3j-37n7SpHjM9-SL9qR6YFo>
Cc: "tls@ietf.org" <TLS@ietf.org>
Subject: Re: [TLS] Would there be security issues with a 0-RTT resume?
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: <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: Sun, 06 Dec 2015 03:32:38 -0000

On Sat, Dec 5, 2015 at 4:46 PM, Eric Rescorla <ekr@rtfm.com> wrote:

> The intention *is* to have a 0-RTT resume, since PSK and 0-RTT should be
> compatible. The spec may not be entirely clear on this point, though.
>
> -Ekr
>

Oh!  Well, that's huge in some ways.  I think the spec could use some more
clarity here :)

Bill