IETF Logo Mail Archive

Re: [http-state] Welcome to http-state

"Adam Barth" <ietf@adambarth.com> Mon, 12 January 2009 20:00 UTC

Return-Path: <http-state-bounces@ietf.org>
X-Original-To: http-state-archive@ietf.org
Delivered-To: ietfarch-http-state-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 410B63A6B61; Mon, 12 Jan 2009 12:00:44 -0800 (PST)
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9FBC3A67FC for <http-state@core3.amsl.com>; Mon, 12 Jan 2009 11:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwMeUAAr8Gjz for <http-state@core3.amsl.com>; Mon, 12 Jan 2009 11:59:47 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 06A7F3A6783 for <http-state@ietf.org>; Mon, 12 Jan 2009 11:59:46 -0800 (PST)
Received: by ey-out-2122.google.com with SMTP id 9so1223890eyd.31 for <http-state@ietf.org>; Mon, 12 Jan 2009 11:59:31 -0800 (PST)
Received: by 10.210.54.17 with SMTP id c17mr12950257eba.35.1231790370918; Mon, 12 Jan 2009 11:59:30 -0800 (PST)
Received: by 10.210.18.3 with HTTP; Mon, 12 Jan 2009 11:59:30 -0800 (PST)
Message-ID: <7789133a0901121159u1da01de8w77edd52913857358@mail.gmail.com>
Date: Mon, 12 Jan 2009 11:59:30 -0800
From: Adam Barth <ietf@adambarth.com>
To: Discuss HTTP State Management Mechanism <http-state@ietf.org>
In-Reply-To: <120206B6A348CA498C70E738A2E963514C0CCC@Nexus.cisecurity.lan>
MIME-Version: 1.0
Content-Disposition: inline
References: <49679299.6060703@corry.biz> <120206B6A348CA498C70E738A2E963514C0CCC@Nexus.cisecurity.lan>
X-Google-Sender-Auth: c6cca0b03b609123
Subject: Re: [http-state] Welcome to http-state
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Discuss HTTP State Management Mechanism <http-state@ietf.org>
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: http-state-bounces@ietf.org
Errors-To: http-state-bounces@ietf.org

On Mon, Jan 12, 2009 at 11:51 AM, Blake Frantz <bfrantz@cisecurity.org> wrote:
> 1. While RFC2109 and draft-pettersen-cookie-v2-03.txt define the
> 'Secure' cookie-av to advise the user-agent against sending the cookie
> over an insecure transport they do not define the desired user-agent
> behavior for cross scheme writing. For example, http://foo.bar
> clobbering a cookie set by https://foo.bar.

Historically, cross-scheme clobbering has been allowed by user agents
because it is impossible to prevent with a bounded amount of storage
(due to eviction of Secure cookies).

Adam
_______________________________________________
http-state mailing list
http-state@ietf.org
https://www.ietf.org/mailman/listinfo/http-state

v2.23.0 | Report a Bug | By Email