[TLS] Cookie reuse subsequent connections
Jānis Čoders <janis.coders@gmail.com> Mon, 30 October 2017 07:07 UTC
Return-Path: <janis.coders@gmail.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 D393C13FE09 for <tls@ietfa.amsl.com>; Mon, 30 Oct 2017 00:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oqCcuPgqLlgY for <tls@ietfa.amsl.com>; Mon, 30 Oct 2017 00:07:43 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 B83C413FE0E for <tls@ietf.org>; Mon, 30 Oct 2017 00:07:43 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id v9so20336445oif.13 for <tls@ietf.org>; Mon, 30 Oct 2017 00:07:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=AbnoLV7XMKuGX5yH1fMAVQElKa4zCLJxCwLpLWwEldM=; b=ludJxvUmm4/tLmL81hzl+7YYT9JageYW4EdGtY9H9W/LoltWovlz0PPEnSnQONLjc9 C6agfg180slGZMw/9ZSKdKv1655144SurgkE71D4AuLHlFhOHO2tT8Jvom6qHypBy5MM 7zugnDEB0H8t6J9iWjQtTLeVeDpCh6ZuB6Z/MFF5gHzuXNQSM5OrDrsqjoWXrlhqLtYZ HVzOE/OH6rMOAEVYuvke8dEUWeD53S0sll/BJoE5dWWqupQq0lVRLDqvSSaokxXMcY9t V9Zf2mPohE70BYo02Y+sim/mVfZPh6fAPEwZXAwD3V5VPk9eGR00PrsnJ8lK0nMRrKwJ wNrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=AbnoLV7XMKuGX5yH1fMAVQElKa4zCLJxCwLpLWwEldM=; b=kCE+aqkngVrTuSqiVy4Ebg0iWwJSFAB0KILsvA5mRMvn9hzPTLpzNdSpI2fTPCEgVb YiO5YoJ0vWMgMi0U5/R3avXuty2Q7t7AjDcFBUZ7faiPN0PdtNYpf6oqkZYhFuhq4DqY 91c/k9X73NZTzLoDUnmWj211dMjVeQcV/bw4g8V5uzw3XTCogxPMCAErqmEs9QpxlA4G Ks/4Ki6PtytmzMW8Wx7MfISKn7QXnSDi9saeUPXM8LyMQ22/xNefwQaoBbslh2W0wuqr Nxes85KLdogpOIaVm2MTYKBUuI/Wy6qcEHQKx+6ojzxEayV2DVBuTzR5mIsyrl/s3vVv OMXw==
X-Gm-Message-State: AMCzsaWFOqmjvlk0msHNzXATK/nKbIEjvx7T+Hp6a5h8AmhgEa0a7TGk vyL9rgrtroR73GINsnaTShkPX5OMM6GccuzZhZA0vA==
X-Google-Smtp-Source: ABhQp+SZ48OXdxytsgw0OXO9bR6Pn8fTww8PAFUQDI+diH7Nv+t2wKHwRWeVv6v5Wr3N5cdmUoRpVsy1GnJat/dhRi8=
X-Received: by 10.157.66.227 with SMTP id c32mr5291189otj.273.1509347262880; Mon, 30 Oct 2017 00:07:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.88.141 with HTTP; Mon, 30 Oct 2017 00:07:42 -0700 (PDT)
From: Jānis Čoders <janis.coders@gmail.com>
Date: Mon, 30 Oct 2017 09:07:42 +0200
Message-ID: <CA+tEvRTBGj0JwQVh66DiFQhrYXdV2h0zOTzAE5MS-yykHe3dLw@mail.gmail.com>
To: tls@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/A6_SzgGDnzAkt0sRYcZgrCD3jz8>
Subject: [TLS] Cookie reuse subsequent connections
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: Mon, 30 Oct 2017 07:07:45 -0000
Hi, is there ANY security issue with reusing Cookie from previous TLS connection? In current draft there is text: "Clients MUST NOT use cookies in their initial ClientHello in subsequent connections." I can't think of any security implication, but can think of situations where it could be useful. -- Ar cieņu, Jānis Čoders
- [TLS] Cookie reuse subsequent connections Jānis Čoders
- Re: [TLS] Cookie reuse subsequent connections Martin Thomson
- Re: [TLS] Cookie reuse subsequent connections Jānis Čoders
- Re: [TLS] Cookie reuse subsequent connections Eric Rescorla
- Re: [TLS] Cookie reuse subsequent connections Benjamin Kaduk
- Re: [TLS] Cookie reuse subsequent connections Jānis Čoders