Re: [TLS] Tickets after key update/post handshake auth

Eric Rescorla <ekr@rtfm.com> Fri, 16 March 2018 16:37 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 DF95F126C83 for <tls@ietfa.amsl.com>; Fri, 16 Mar 2018 09:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 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_LOW=-0.7] 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 9anYz0Rbyodl for <tls@ietfa.amsl.com>; Fri, 16 Mar 2018 09:37:07 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 2007D1200C5 for <tls@ietf.org>; Fri, 16 Mar 2018 09:37:07 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id j73so4232917qke.6 for <tls@ietf.org>; Fri, 16 Mar 2018 09:37:07 -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=+tl9MxY9yBofGBkpLn9lFKqmaLtmGj/QlLU2eIZfaig=; b=tHO6wsM3GsmMZC9epqK759MQxV7rq22yPaJqqGmbFve+DrQy+mFH+p3SotmBjY4ap8 0PShVqmUwof+QxnsmRns80C9cCTYP7n+EgYfie3eZh7HO516qQc8yElhSnqzNDFPZXJy EiohfwEUEh0aqozutaA0qX/wxXeSfWjoEsFopCdGKVx34JI1BjL6ynBb9Xm1Qm3qiz69 pqsA+YycQSBca8dHDoQKOmy0zIwmQ2RGc6gtfG+0QYTP+hzx5/Fa+8Ao6yHL01Rh85Oj 5RnY/9AzQxBgD6qq3p1/AqCVVVcrN/DAplPmKMs4HLuOpqnjfLqT1IHgcjBJT7NmWgYW I/cA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+tl9MxY9yBofGBkpLn9lFKqmaLtmGj/QlLU2eIZfaig=; b=IyiJ1BZ5c3y/i6xaeb5i2oNbVeGzQY2X64v2W6xYjoQvsucRJF7nzehrYWAmgDg5d2 68q8Y4J4Oj1bbcKMaz7ulR3t/9hR/n7CyNgGtazc8guwNKYALSJ9482F0NsCtMxxpff9 TKse+NeAykBPER+0ukjOmolNwznzcBuMVEnSeSzCx2irym8AT+OwE4i9P4q9Q0Ja8X5x pTrggPirEFbGyTOK6e9jJMFYsP5e6NLgZanSK4y0aN2X9pS1wCt7DfighMJxNg4xw08c CiL0HPW3i8zJ180QHYrFhSnLNwmQsADsZf8xaOfK+AdB1Fkl4iXQ1YhbK/g7PjlCTZ3g 9k5g==
X-Gm-Message-State: AElRT7GiC3C0qzywEUKiL9OBZd0CXdqgG31OKko5eddOk3864eWuQzjU IybFDukDYcl78ZoXFjt6S+V+ZwsFISpqxrv8Hu5OQUHS
X-Google-Smtp-Source: AG47ELuQfLaDsA+VBAIvvT+3UQ7f/QLmZxigmMYKTJ8BuerriY2N7lTfeeTK+2psoQtwMyZDWSqv1w3EpZplEaaBQyI=
X-Received: by 10.55.192.151 with SMTP id v23mr3603255qkv.83.1521218226145; Fri, 16 Mar 2018 09:37:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.37.234 with HTTP; Fri, 16 Mar 2018 09:36:25 -0700 (PDT)
In-Reply-To: <54b7e8df-705c-64dc-9011-b0d2acc2950b@openssl.org>
References: <54b7e8df-705c-64dc-9011-b0d2acc2950b@openssl.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 16 Mar 2018 16:36:25 +0000
Message-ID: <CABcZeBNMFs0mGOkSq+oqw2LCDhZxfTzbrCWPYozVihiPED+Hxg@mail.gmail.com>
To: Matt Caswell <matt@openssl.org>
Cc: "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="001a114797c6fee2f405678a372a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Z7C5Dcf-5dk_VKJelKFmcSAD6eM>
Subject: Re: [TLS] Tickets after key update/post handshake auth
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 16 Mar 2018 16:37:09 -0000

On Fri, Mar 16, 2018 at 4:19 PM, Matt Caswell <matt@openssl.org> wrote:

> What is reasonable behaviour for a client to do with any tickets it has
> previously received following a key update or a post-handshake
> authentication? Should those old tickets be now considered out-of-date
> and not used?
>

There is no good reason to discard tickets received post KeyUpdate. The
KeyUpdate
has no impact on their security.

It's probably reasonable to discard tickets received after Post-Handshake
Auth if a new
ticket is received, as that ticket might incorporate the client's
authenticated identity. Otherwise
I wouldn't bother.

-Ekr


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