IETF Logo Mail Archive

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

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 01 April 2015 12:12 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 2DAA71A896A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Apr 2015 05:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.512
X-Spam-Level:
X-Spam-Status: No, score=-14.512 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, USER_IN_DEF_DKIM_WL=-7.5] 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 PYLEEziaWcea for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Apr 2015 05:12:46 -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 7B5A41A8969 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 1 Apr 2015 05:12:46 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YdHSY-0006UA-Qc for ietf-http-wg-dist@listhub.w3.org; Wed, 01 Apr 2015 12:09:26 +0000
Resent-Date: Wed, 01 Apr 2015 12:09:26 +0000
Resent-Message-Id: <E1YdHSY-0006UA-Qc@frink.w3.org>
Received: from madai.w3.org ([203.178.154.97] helo=madai.keio.w3.org) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <evyncke@cisco.com>) id 1YdHST-0006DW-U7 for ietf-http-wg@listhub.w3.org; Wed, 01 Apr 2015 12:09:22 +0000
Received: from rcdn-iport-1.cisco.com ([173.37.86.72]) by madai.keio.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <evyncke@cisco.com>) id 1YdHEd-0006CD-8c for ietf-http-wg@w3.org; Wed, 01 Apr 2015 11:55:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2042; q=dns/txt; s=iport; t=1427889303; x=1429098903; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=bIswVvHtI/TNXqeZNRD5/taF0zmhBPEaJC9oK9ALGS4=; b=bEW/YhshCDxx5z53+YR1+h5BN58+eL8VgmW5xhopvdtaW10rfpW1TG1y U99MEBs7le30EDg0h4/fP+Mhg07ZrO2afI7js1j9/7uVtxc5aPAIK1hrX aKu842OdCn+KqlGjEu1NC9MoJYnWwLqa1LTcutvL02jBTn9605oSRRyzG 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQC52xtV/4ENJK1cgwZSXAWDEMJHhXMCHIEkTAEBAQEBAX2EFQEBAgIjEUUQAgEIDgoCAiYCAgIwFRACBA4FCYgmDbRSmSkBAQEBAQEBAQEBAQEBAQEBAQEBGYEhigiERTMHgmiBRQWQY4NyhgSUPiKCAhyBUG8BgUN/AQEB
X-IronPort-AV: E=Sophos;i="5.11,503,1422921600"; d="scan'208";a="405226636"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-1.cisco.com with ESMTP; 01 Apr 2015 11:52:22 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t31BqMhV009079 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 11:52:22 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.130]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 06:52:22 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Willy Tarreau <w@1wt.eu>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Thread-Topic: Linking a cookie to an IP address is a very bad in 2015...
Thread-Index: AQHQbG+Fl9W4nlcIVkGcZNdWVbT8WZ04XdUAgAAjQ4A=
Date: Wed, 01 Apr 2015 11:52:04 +0000
Message-ID: <D141A868.41491%evyncke@cisco.com>
References: <D141A3E5.4146E%evyncke@cisco.com> <20150401114608.GA7832@1wt.eu>
In-Reply-To: <20150401114608.GA7832@1wt.eu>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.6.141106
x-originating-ip: [10.55.185.71]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0E9818C637242E4BB45B3571A93F207E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Received-SPF: pass client-ip=173.37.86.72; envelope-from=evyncke@cisco.com; helo=rcdn-iport-1.cisco.com
X-W3C-Hub-Spam-Status: No, score=-11.6
X-W3C-Hub-Spam-Report: DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, W3C_NW=1
X-W3C-Scan-Sig: madai.keio.w3.org 1YdHEd-0006CD-8c a20a36f0c8e844580d3b080b1267e497
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/D141A868.41491%25evyncke@cisco.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29176
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>

Indeed, people never learn...

OTOH, linking a session cookie to the user-agent IP address renders
'session cookie stealing' much more difficult

-éric

On 1/04/15 13:46, "Willy Tarreau" <w@1wt.eu> wrote:

>On Wed, Apr 01, 2015 at 11:32:05AM +0000, Eric Vyncke (evyncke) 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)
>
>I'm amazed people still do that in 2015, I had the idea to do it in 1999
>until I realized it was stupid and never did it! So I'd have guessed that
>16 years later everyone would have also figured this! If IP addresses
>were stable during a session, cookies would not be needed, the address
>would be used instead. So it's precisely because addresses are unreliable
>that cookies exist.
>
>Too bad people don't learn from others' mistakes...
>
>Willy
>

v2.23.0 | Report a Bug | By Email