[TLS] Tickets after key update/post handshake auth
Matt Caswell <matt@openssl.org> Fri, 16 March 2018 16:19 UTC
Return-Path: <matt@openssl.org>
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 BE9AD12D80F for <tls@ietfa.amsl.com>; Fri, 16 Mar 2018 09:19:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=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 1qebNsh60Pvv for <tls@ietfa.amsl.com>; Fri, 16 Mar 2018 09:19:53 -0700 (PDT)
Received: from mta.openssl.org (xmpp.openssl.org [194.97.150.230]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1415C126C83 for <tls@ietf.org>; Fri, 16 Mar 2018 09:19:53 -0700 (PDT)
Received: from [10.3.10.6] (ip-50-84-52-196.southampton.uk.amsterdamresidential.com [196.52.84.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta.openssl.org (Postfix) with ESMTPSA id 7907CE4C57 for <tls@ietf.org>; Fri, 16 Mar 2018 16:19:50 +0000 (UTC)
To: "tls@ietf.org" <tls@ietf.org>
From: Matt Caswell <matt@openssl.org>
Message-ID: <54b7e8df-705c-64dc-9011-b0d2acc2950b@openssl.org>
Date: Fri, 16 Mar 2018 16:19:49 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/JTpBhm-OW79qfMkCanNgrXu4o6A>
Subject: [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:19:55 -0000
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? Matt
- [TLS] Tickets after key update/post handshake auth Matt Caswell
- Re: [TLS] Tickets after key update/post handshake… Eric Rescorla
- Re: [TLS] Tickets after key update/post handshake… Hubert Kario
- Re: [TLS] Tickets after key update/post handshake… Martin Thomson