Re: [Jmap] JMAP security
Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 09 February 2017 17:32 UTC
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21573129C25 for <jmap@ietfa.amsl.com>; Thu, 9 Feb 2017 09:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
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 GpSqM1faz9Og for <jmap@ietfa.amsl.com>; Thu, 9 Feb 2017 09:32:42 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0C23129C29 for <jmap@ietf.org>; Thu, 9 Feb 2017 09:32:41 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 486C4CEC00C; Thu, 9 Feb 2017 17:32:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1486661559; bh=9iUT0w0H15Q7FgO6j8mNITt/7R1EDbemN+usB2lmgdQ=; h=From:To:Subject:Date:References:From; b=CZajRQrCzGs2xyjBK3NqFVLnpFkJq9Efm6HTuxi36HWkB+8o4Y5LKOiC9LQdtjmuc t8bIH4ovQbddFM/A15ZLkx8TIJBDS8MCFt576ZmztfBVsf5lKGXvsR2hnv5svFRUqS ukGfzXkX0AlS+k2QLA5IVpZ5kYG4cjcO4p3PI7z4=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1486661558-2178-25938/12/5; Thu, 9 Feb 2017 17:32:38 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: jmap@ietf.org, Yoav Nir <ynir.ietf@gmail.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Дмитрий Подкорытов <podkorytov@mail.ru>
Date: Thu, 09 Feb 2017 18:32:36 +0100
Message-Id: <cCbkcpqiY8ZcxnR8+fLtaq5XdXgwv58AnZdxszv0WkU=.sha-256@antelope.email>
References: <yw8pj50om7igw8xwxd2fon4q.1486574928465@email.android.com> <4ABF6702-BFC7-4530-95FD-C61C06F2E6AB@gmail.com> <1486658028.81835495@f105.i.mail.ru> <fa8990fd-a17b-a3ae-b251-6d97431c74b6@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/ar78-hHnS9wRD7gH59ZkKYlgtmc>
Subject: Re: [Jmap] JMAP security
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:32:44 -0000
It sounds like a straightforward origin problem. Perhaps the security considerations should mention the origin headers. Or they may do already, that is the kind of near-boilerplate I would hardly even notice. Arnt
- [Jmap] JMAP security podkorytov
- Re: [Jmap] JMAP security Yoav Nir
- Re: [Jmap] JMAP security Дмитрий Подкорытов
- Re: [Jmap] JMAP security Alexey Melnikov
- Re: [Jmap] JMAP security Yoav Nir
- Re: [Jmap] JMAP security Arnt Gulbrandsen