IETF Logo Mail Archive

Re: Linking a cookie to an IP address is a very bad in 2015...

Zhong Yu <zhong.j.yu@gmail.com> Thu, 02 April 2015 16:43 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF3E1ACE60 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 2 Apr 2015 09:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 VGMQuM7o5rL5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 2 Apr 2015 09:43:49 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180491ACE2B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 2 Apr 2015 09:43:49 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YdiAK-0006XL-CK for ietf-http-wg-dist@listhub.w3.org; Thu, 02 Apr 2015 16:40:24 +0000
Resent-Date: Thu, 02 Apr 2015 16:40:24 +0000
Resent-Message-Id: <E1YdiAK-0006XL-CK@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <zhong.j.yu@gmail.com>) id 1YdiAH-0006We-5t for ietf-http-wg@listhub.w3.org; Thu, 02 Apr 2015 16:40:21 +0000
Received: from mail-ob0-f172.google.com ([209.85.214.172]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <zhong.j.yu@gmail.com>) id 1YdiAG-0008Ir-6A for ietf-http-wg@w3.org; Thu, 02 Apr 2015 16:40:21 +0000
Received: by obbfy7 with SMTP id fy7so52475089obb.2 for <ietf-http-wg@w3.org>; Thu, 02 Apr 2015 09:39:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nRe04o9MtzioTCm78OXSGN9Vs3jI3RdvrKJiYcUe3Ss=; b=v+0qHc3l5rxjXHAB5VZ2Y+22XmOjHlii0/FNCIhBFw3+o0Ks6K5Zo6TOvyhCiXDRdm 8kzZm82aiuyc01Zv6vVrRo4c7LUn4B3mXVGwP69wfg7XG8LX/VG9P6v2lrJoAmYi11ip zLaEHW2YQDA5VQNeEjpRhQRZZriEQlUm9eXGdtFWhsr/ha7xa3HACuHKlSbUMliXqO5q YCFviHqb/Q38WqCVruU1Lmtndw9C69KTU/fkBC7lGN/1E8LjgflydyeF8saQD/k4WOAq 48zwm354BcAgHDdtBtDEjpYJTp+oxOgKpyZSe9LV2cLrtA7fbvu5wrOJ3V63+MzysdXp 4/ag==
MIME-Version: 1.0
X-Received: by 10.182.24.97 with SMTP id t1mr47391585obf.77.1427992794411; Thu, 02 Apr 2015 09:39:54 -0700 (PDT)
Received: by 10.76.175.9 with HTTP; Thu, 2 Apr 2015 09:39:54 -0700 (PDT)
In-Reply-To: <CABkgnnXF72bcAF7STJTwi8c-WmBNWx4GppvW=1HKX7cNX6jWcg@mail.gmail.com>
References: <D141A3E5.4146E%evyncke@cisco.com> <CACuKZqHDru45jcZiDt91gVtrTZZqJJ2XaK6k0XVKK0R4nCciFg@mail.gmail.com> <CABkgnnXF72bcAF7STJTwi8c-WmBNWx4GppvW=1HKX7cNX6jWcg@mail.gmail.com>
Date: Thu, 02 Apr 2015 11:39:54 -0500
Message-ID: <CACuKZqEw=v8CbOPbRxVXVNOKj_rGt_v4ENVzwaWbC8C1vw9oNQ@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.214.172; envelope-from=zhong.j.yu@gmail.com; helo=mail-ob0-f172.google.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-1.685, 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, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1YdiAG-0008Ir-6A 455a3773a254d9f970bf3aa7da5ff6cf
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Linking a cookie to an IP address is a very bad in 2015...
Archived-At: <http://www.w3.org/mid/CACuKZqEw=v8CbOPbRxVXVNOKj_rGt_v4ENVzwaWbC8C1vw9oNQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29220
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Thu, Apr 2, 2015 at 11:19 AM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> On 2 April 2015 at 09:11, Zhong Yu <zhong.j.yu@gmail.com> wrote:
>> The server can bind state to the TLS
>> session; there's no need for an HTTP cookie, if the site is HTTPS
>> only.
>
> I always recommend against that.  Connections break.

The new connection will like reuse the same TLS session[1]. The
browser is not required to do that, but from my tests,
firefox/IE/chrome on Windows apparently do.

Zhong Yu

[1] http://en.wikipedia.org/wiki/Transport_Layer_Security#Resumed_TLS_handshake

v2.46.0 | Report a Bug | By Email | System Status