Re: Trust and provacy problems with draft-loreto-httpbis-explicitly-auth-proxy

Raphaël Durand <mail@raphaeldurand.fr> Tue, 06 May 2014 19:49 UTC

Return-Path: <mail@raphaeldurand.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A32A1A03B5 for <ietf@ietfa.amsl.com>; Tue, 6 May 2014 12:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.2
X-Spam-Level:
X-Spam-Status: No, score=0.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_EMBEDS=1.799, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3] autolearn=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 gmAHSEBBLPXC for <ietf@ietfa.amsl.com>; Tue, 6 May 2014 12:49:46 -0700 (PDT)
Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:c:538::195]) by ietfa.amsl.com (Postfix) with ESMTP id ECDD71A018D for <ietf@ietf.org>; Tue, 6 May 2014 12:49:45 -0700 (PDT)
Received: from [IPv6:2a01:6600:8080:5600:1904:8efc:eedd:3725] (unknown [IPv6:2a01:6600:8080:5600:1904:8efc:eedd:3725]) (Authenticated sender: ipv6@ultrawaves.fr) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 32C75A8075 for <ietf@ietf.org>; Tue, 6 May 2014 21:49:39 +0200 (CEST)
Message-ID: <53693CCA.6050206@raphaeldurand.fr>
Date: Tue, 06 May 2014 21:49:30 +0200
From: Raphaël Durand <mail@raphaeldurand.fr>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Trust and provacy problems with draft-loreto-httpbis-explicitly-auth-proxy
References: <536775D2.4090708@raphaeldurand.fr> <C2A9DEB3-2ED6-45B5-92F6-C455D2C5A1ED@ericsson.com>
In-Reply-To: <C2A9DEB3-2ED6-45B5-92F6-C455D2C5A1ED@ericsson.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="raKbPlTv5M3QrIqluhDDphohJT5WQIsj4"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KFib8Uc84DrsDr70s9FcfaOqPH4
X-Mailman-Approved-At: Wed, 07 May 2014 08:16:22 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 19:49:48 -0000

Hello Salavatore.

Le 06/05/2014 13:27, Salvatore Loreto a écrit :
> Hi Raphael,
>
> first let me clarify once again: https resources are not affected by
> the explicitly authenticated proxy
> the draft only propose to proxy the http:// resources.
>
But one of the aim of HTTP2 is to make TLS 1.2 (or greater) mandatory,
the same way HTTPS does.
Add to this that most browsers have skipped the http or https part of an
URI, what will be the difference between http and https ?

In my opinion, with HTTP2 and mandatory encryption, HTTPS will no longer
exist. (except maybe for the handling of the X.509 trust model)
We have to deal all the encrypted flow in the same way. Any exception
would be fatal.

Best regards.
Raphaël Durand