Re: Linking a cookie to an IP address is a very bad in 2015...
Max Bruce <max.bruce12@gmail.com> Fri, 03 April 2015 07: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 0B4A31A914A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Apr 2015 00:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 PMRbXsxMIFdc for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Apr 2015 00:16:15 -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 D40091A9145 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 3 Apr 2015 00:16:15 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ydvnc-0002t0-BG for ietf-http-wg-dist@listhub.w3.org; Fri, 03 Apr 2015 07:13:52 +0000
Resent-Date: Fri, 03 Apr 2015 07:13:52 +0000
Resent-Message-Id: <E1Ydvnc-0002t0-BG@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <max.bruce12@gmail.com>) id 1YdvnZ-0002mV-LK for ietf-http-wg@listhub.w3.org; Fri, 03 Apr 2015 07:13:49 +0000
Received: from mail-ie0-f178.google.com ([209.85.223.178]) by lisa.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <max.bruce12@gmail.com>) id 1YdvnY-0001wV-QZ for ietf-http-wg@w3.org; Fri, 03 Apr 2015 07:13:49 +0000
Received: by iedfl3 with SMTP id fl3so96811318ied.1 for <ietf-http-wg@w3.org>; Fri, 03 Apr 2015 00:13:23 -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=KtgH6j8k6GS7Z++AZf5GFB3iKN6T3yPvNLnROX5FOj0=; b=K+fQitCKIzIr7kXq/Y9wvLIPkMXLkrqdCbInTz9bjJQMXxa+ssJzlFIyjAFWct+p2f 4OZynwBGxazdb7+gTfA57UhfIEP1+YpQhOpvWGeG9Kl2/CVR5ZVGJsgFqrwvx14JeDIq poHwcoXOIg/dn+PruiHx9TtEhObxr7013QZppVTjSaIz4PziUMQ9yoU1o4c0bALTrX3o xsgsos40RIpUESNBd2fBNAqEeKFo6MomIWcNWWuJfFwaps/f3x/RkJHLvlPtzYIvVURC br0EO8iPNBgRr0na8fBGzOZvE6l+5yP50POWZo5gTq3M9mQ5roXcGXiq0yVMTYyu1Ynh +mlA==
MIME-Version: 1.0
X-Received: by 10.107.129.88 with SMTP id c85mr1715383iod.81.1428045203061; Fri, 03 Apr 2015 00:13:23 -0700 (PDT)
Received: by 10.36.58.142 with HTTP; Fri, 3 Apr 2015 00:13:22 -0700 (PDT)
In-Reply-To: <551E3D00.5090501@mathemainzel.info>
References: <D141A3E5.4146E%evyncke@cisco.com> <20150401114608.GA7832@1wt.eu> <04DD393C-711F-4C9E-B21C-B184B8972DFC@apple.com> <20150401150716.GA7871@1wt.eu> <25C792A9-56D0-452D-A46C-561A44E4F229@manico.net> <20150401151634.GB7871@1wt.eu> <CABb0SYQ5=5BHSH-JQ5XsCi_bQ8h5FN=WNPvAYkzy94Bm=yTVwg@mail.gmail.com> <551E3D00.5090501@mathemainzel.info>
Date: Fri, 03 Apr 2015 00:13:22 -0700
Message-ID: <CABb0SYQAOXRWL5TvD5H5g_4VDwLxF=6kzhmVgCSK8Pv7pq8Apw@mail.gmail.com>
From: Max Bruce <max.bruce12@gmail.com>
To: "Walter H." <Walter.H@mathemainzel.info>
Cc: Michael Sweet <msweet@apple.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a113f92fe0d427a0512ccafe2"
Received-SPF: pass client-ip=209.85.223.178; envelope-from=max.bruce12@gmail.com; helo=mail-ie0-f178.google.com
X-W3C-Hub-Spam-Status: No, score=-4.4
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 1YdvnY-0001wV-QZ 51bf3a3fe662d57787067c29283b50b4
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/CABb0SYQAOXRWL5TvD5H5g_4VDwLxF=6kzhmVgCSK8Pv7pq8Apw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29231
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>
When you say transmitting from host to server, what do you mean? And yes, if I understand what your asking. It effectively compiled a random hash, and then enforced an IP & user agent. I have recently removed the IP enforecement though. On Fri, Apr 3, 2015 at 12:10 AM, Walter H. <Walter.H@mathemainzel.info> wrote: > On 01.04.2015 21:48, Max Bruce wrote: > > What about linking to several? I wrote a session system for my Web Server > that will only allow access to the original Session ID if the IP & > User-Agent has remained unchanged, in order to protect against session > hijacking. I've found it's highly effective, unless you IP Spoof. > > what kind of mechanism do you use for transmitting the Session ID from > host to server? > does it prevent access from an ident configured but different host behind > a NAT? >
- Linking a cookie to an IP address is a very bad i… Eric Vyncke (evyncke)
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Eric Vyncke (evyncke)
- Re: Linking a cookie to an IP address is a very b… Michael Sweet
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Max Bruce
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Max Bruce
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Michael Sweet
- Re: Linking a cookie to an IP address is a very b… Michael Sweet
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Eric Vyncke (evyncke)
- Re: Linking a cookie to an IP address is a very b… Eric Vyncke (evyncke)
- Re: Linking a cookie to an IP address is a very b… Michael Sweet
- Re: Linking a cookie to an IP address is a very b… Zhong Yu
- Re: Linking a cookie to an IP address is a very b… Martin Thomson
- Re: Linking a cookie to an IP address is a very b… Zhong Yu
- Re: Linking a cookie to an IP address is a very b… Zhong Yu
- Re: Linking a cookie to an IP address is a very b… Martin Thomson
- Re: Linking a cookie to an IP address is a very b… Zhong Yu
- Re: Linking a cookie to an IP address is a very b… Michael Sweet
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Walter H.
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Walter H.
- Re: Linking a cookie to an IP address is a very b… Willy Tarreau
- Re: Linking a cookie to an IP address is a very b… Walter H.
- Re: Linking a cookie to an IP address is a very b… Max Bruce
- Re: Linking a cookie to an IP address is a very b… Walter H.
- Re: Linking a cookie to an IP address is a very b… Max Bruce
- Re: Linking a cookie to an IP address is a very b… Eric Vyncke (evyncke)
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Walter H.
- Re: Linking a cookie to an IP address is a very b… Walter H.
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Max Bruce
- Re: Linking a cookie to an IP address is a very b… Max Bruce
- Re: Linking a cookie to an IP address is a very b… Jim Manico
- Re: Linking a cookie to an IP address is a very b… Eric Vyncke (evyncke)
- Re: Linking a cookie to an IP address is a very b… Walter H.