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:16 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 9F4AB1B2D4C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 2 Apr 2015 09:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.412
X-Spam-Level:
X-Spam-Status: No, score=-6.412 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_52=0.6, 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 IUspooCWw4O5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 2 Apr 2015 09:16:28 -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 178221B2D40 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 2 Apr 2015 09:16:25 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ydhih-0008U7-Ht for ietf-http-wg-dist@listhub.w3.org; Thu, 02 Apr 2015 16:11:51 +0000
Resent-Date: Thu, 02 Apr 2015 16:11:51 +0000
Resent-Message-Id: <E1Ydhih-0008U7-Ht@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 1Ydhid-0008TL-7Q for ietf-http-wg@listhub.w3.org; Thu, 02 Apr 2015 16:11:47 +0000
Received: from mail-ob0-f173.google.com ([209.85.214.173]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <zhong.j.yu@gmail.com>) id 1Ydhic-0006zy-4p for ietf-http-wg@w3.org; Thu, 02 Apr 2015 16:11:47 +0000
Received: by obbgh1 with SMTP id gh1so129080597obb.1 for <ietf-http-wg@w3.org>; Thu, 02 Apr 2015 09:11:20 -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:content-transfer-encoding; bh=WhRqZxvCwsptNMEPO36RhFwFYMk4Sum4p9Dff5f7T9I=; b=rO0F/7/m2Bf7ezxLx81kUXp6aeSBPRsmDs2zLxbU5zohiWglEDVfytCalUKWs4glQP jbGJB/doONatzW6eDe/b7DEala1b6BYnY9QMuOqK1rtYbm8fYzF2PNlWA7SoDVs6pnaV qBT50Zc/hgzmHSQztmDovB6d4Figk6VdCYhCIhArNRDGbyR/G2mPiWkWn6ITI6Q0bZP+ FGHTst81/vWwU8eC/paewXt2JimNwqzhb5KNYyguqLckFtWnR7dU2POksyZiegiPBZhC 99zowoOuBUpDPMR1nl1wka7tjCHmUlGBkz2wQuZwBHEESgRxmnjSviypVDz0ZENTUEjt bICg==
MIME-Version: 1.0
X-Received: by 10.60.101.195 with SMTP id fi3mr15081485oeb.65.1427991080057; Thu, 02 Apr 2015 09:11:20 -0700 (PDT)
Received: by 10.76.175.9 with HTTP; Thu, 2 Apr 2015 09:11:19 -0700 (PDT)
In-Reply-To: <D141A3E5.4146E%evyncke@cisco.com>
References: <D141A3E5.4146E%evyncke@cisco.com>
Date: Thu, 02 Apr 2015 11:11:19 -0500
Message-ID: <CACuKZqHDru45jcZiDt91gVtrTZZqJJ2XaK6k0XVKK0R4nCciFg@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.214.173; envelope-from=zhong.j.yu@gmail.com; helo=mail-ob0-f173.google.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-1.696, 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 1Ydhic-0006zy-4p 4813aa6f1f32d194fb8630c0961f40fd
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/CACuKZqHDru45jcZiDt91gVtrTZZqJJ2XaK6k0XVKK0R4nCciFg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29217
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>

A TLS session is a pretty good alternative. Within one browser
session, different HTTPS connections to the same server will likely
share the same TLS session. The server can bind state to the TLS
session; there's no need for an HTTP cookie, if the site is HTTPS
only.

Zhong Yu
bayou.io



On Wed, Apr 1, 2015 at 6:32 AM, Eric Vyncke (evyncke) <evyncke@cisco.com> wrote:
> In the era of scarce IPv4 addresses, servers should NOT link the HTTP
> session cookies to the user-agent IP address...
>
> I have posted in the IETF V6OPS WG the following:
> http://www.ietf.org/proceedings/92/slides/slides-92-v6ops-6.pdf
> https://tools.ietf.org/html/draft-vyncke-v6ops-happy-eyeballs-cookie
>
> In short, heavy use of NAT and/or dual-stack (IPv4/IPv6) can cause a change
> of user-agent address => lost of session.
>
> Any suggestion on how this can be addressed? I know at least two major web
> sites in Belgium that removed IPv6 from their web site due to this issue
> (and their security department not wanting to unlink IP address from the
> session cookies)
>
> Comments are welcome
>
> -éric
>

v2.23.0 | Report a Bug | By Email