IETF Logo Mail Archive

Re: [websec] Same Origins and email

Adam Barth <ietf@adambarth.com> Mon, 12 December 2011 19:09 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 934E521F8ACA for <websec@ietfa.amsl.com>; Mon, 12 Dec 2011 11:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kekDl3K-ShW for <websec@ietfa.amsl.com>; Mon, 12 Dec 2011 11:09:25 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0C49321F8ABE for <websec@ietf.org>; Mon, 12 Dec 2011 11:09:24 -0800 (PST)
Received: by qcsf15 with SMTP id f15so4556565qcs.31 for <websec@ietf.org>; Mon, 12 Dec 2011 11:09:24 -0800 (PST)
Received: by 10.50.183.201 with SMTP id eo9mr16866728igc.79.1323716964207; Mon, 12 Dec 2011 11:09:24 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id r18sm33181724ibh.4.2011.12.12.11.09.22 (version=SSLv3 cipher=OTHER); Mon, 12 Dec 2011 11:09:23 -0800 (PST)
Received: by iaek3 with SMTP id k3so10750994iae.31 for <websec@ietf.org>; Mon, 12 Dec 2011 11:09:22 -0800 (PST)
Received: by 10.50.183.201 with SMTP id eo9mr16866650igc.79.1323716962127; Mon, 12 Dec 2011 11:09:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.159.138 with HTTP; Mon, 12 Dec 2011 11:08:51 -0800 (PST)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C15518@EXCH-C2.corp.cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C15518@EXCH-C2.corp.cloudmark.com>
From: Adam Barth <ietf@adambarth.com>
Date: Mon, 12 Dec 2011 11:08:51 -0800
Message-ID: <CAJE5ia8mDSjr6ww3uduUP_SQV2i9CB5cpuLDzL1tj8MvWb8PcA@mail.gmail.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: "websec@ietf.org" <websec@ietf.org>
Subject: Re: [websec] Same Origins and email
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 19:09:25 -0000

On Mon, Dec 12, 2011 at 11:01 AM, Murray S. Kucherawy <msk@cloudmark.com> wrote:
> Hi all, long-time lurker, first-time poster.
>
> I don’t work in the web browser business so much as I do the messaging
> anti-abuse business.  But this stuff has gotten my attention.  Now that
> RFC6454 is published, I have a few questions about its possible application
> in my context.
>
> My first question (probably of several): What is the origin of an HTML
> document when it’s viewed in an HTML-aware MUA because it arrived by email?

That depends on the MUA.  In Gmail, for example, the origin is
https://mail.google.com.  It depends on the URL the MUA assigns to the
HTML document contained in the email.

Adam

v2.23.0 | Report a Bug | By Email