Re: HTTP Alternative Services: What about TLS client certificates?

"Roy T. Fielding" <fielding@gbiv.com> Mon, 30 March 2015 22:35 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 C48AE1A6F32 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Mar 2015 15:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 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] 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 I1mcR4cxrZs3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Mar 2015 15:35:36 -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 A1BBB1A6F2B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 30 Mar 2015 15:35:36 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YciEQ-0005qd-5d for ietf-http-wg-dist@listhub.w3.org; Mon, 30 Mar 2015 22:32:30 +0000
Resent-Date: Mon, 30 Mar 2015 22:32:30 +0000
Resent-Message-Id: <E1YciEQ-0005qd-5d@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <fielding@gbiv.com>) id 1YciEI-0005p6-U8 for ietf-http-wg@listhub.w3.org; Mon, 30 Mar 2015 22:32:22 +0000
Received: from sub4.mail.dreamhost.com ([69.163.253.135] helo=homiemail-a31.g.dreamhost.com) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <fielding@gbiv.com>) id 1YciEH-0004ai-SG for ietf-http-wg@w3.org; Mon, 30 Mar 2015 22:32:22 +0000
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 1BC71202043; Mon, 30 Mar 2015 15:32:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=5L8kfTXzua+YP9jKHIvaDdrnvGE=; b=S5mfzzcvf4gY/7FCk1z826gMDGAk cSMaJzu2Pl1FzDUK+1sZ8DNb67uzl4sO0Sa8LSFprpP+KZZ0iBcHChYH+FCa2/c5 1CXqX/2G2EzDeaLPlR8WPNGxtO3uTyvhTh2XXxOfz0alz6VY/qj+yVRHEi+GEFVY 2BLWZTv+Db5NoTk=
Received: from [192.168.1.12] (ip68-228-83-124.oc.oc.cox.net [68.228.83.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id DDB3220203C; Mon, 30 Mar 2015 15:31:59 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <CAP+FsNccBcdYDRKjNt-i4o6LqZCQhxHL5QZhMRrHMGoq0cqwYw@mail.gmail.com>
Date: Mon, 30 Mar 2015 15:31:59 -0700
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, Jann Horn <jann@thejh.net>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEA50C88-690B-4DF0-9454-05A87324926D@gbiv.com>
References: <20150329211205.GA17881@pc.thejh.net> <64B360B0-BE02-48FB-BBC5-6F4706433BD2@gbiv.com> <20150330172622.GA15624@LK-Perkele-VII> <156E435D-13EC-404A-909C-4E554280BA0C@gbiv.com> <CAP+FsNccBcdYDRKjNt-i4o6LqZCQhxHL5QZhMRrHMGoq0cqwYw@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
X-Mailer: Apple Mail (2.1283)
Received-SPF: none client-ip=69.163.253.135; envelope-from=fielding@gbiv.com; helo=homiemail-a31.g.dreamhost.com
X-W3C-Hub-Spam-Status: No, score=-7.8
X-W3C-Hub-Spam-Report: AWL=1.176, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1YciEH-0004ai-SG a322063b35b6590244e450eac00bf223
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP Alternative Services: What about TLS client certificates?
Archived-At: <http://www.w3.org/mid/CEA50C88-690B-4DF0-9454-05A87324926D@gbiv.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29094
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>

On Mar 30, 2015, at 1:15 PM, Roberto Peon wrote:

> I think the point of the alt-svc field is to declare that the new transport and port are the same origin in this case.

Well, then Alt-Svc is a security hole.  Creating a security hole just
to avoid one duplicate request (retrieving the alternative service
before doing subrequests) would completely abuse the point of switching
to a TLS connection for that service.

A simple principle is that no header field from the response origin
can be allowed to change the same-origin for that response.  Only a
field from the target can do that safely (e.g., CORS).

....Roy