Re: HTTP/2 and Pervasive Monitoring
"Martin Nilsson" <nilsson@opera.com> Fri, 15 August 2014 12:46 UTC
Return-Path: <ietf-http-wg-request@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 C830F1A0A91 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Aug 2014 05:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.57
X-Spam-Level:
X-Spam-Status: No, score=-7.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ZkDNRsxOPBYN for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Aug 2014 05:46:38 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 062881A0A7B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 15 Aug 2014 05:46:38 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XIGre-0000hP-7q for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Aug 2014 12:44:14 +0000
Resent-Date: Fri, 15 Aug 2014 12:44:14 +0000
Resent-Message-Id: <E1XIGre-0000hP-7q@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <nilsson@opera.com>) id 1XIGrM-0000di-6n for ietf-http-wg@listhub.w3.org; Fri, 15 Aug 2014 12:43:56 +0000
Received: from mail-we0-f178.google.com ([74.125.82.178]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <nilsson@opera.com>) id 1XIGrL-0007Oj-8v for ietf-http-wg@w3.org; Fri, 15 Aug 2014 12:43:56 +0000
Received: by mail-we0-f178.google.com with SMTP id w61so2320562wes.9 for <ietf-http-wg@w3.org>; Fri, 15 Aug 2014 05:43:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:to:subject:references:date :mime-version:content-transfer-encoding:from:organization:message-id :in-reply-to:user-agent; bh=82cKN4Y9H64zP9bJBuNOPROwaHUKwnh4lHNYoxPrdd0=; b=LCnKgGVd/IaMbiNR6J6V85qSWeOGGUMqce6TnSCM8EetLtoHQEhqjccqFbD51yEbYW 8vHz9aftGYG0AbAMCjAQvdp3hivO+rmiSdzWtOoFOuag3Z2wC86AbAii3vTCsKY7TG/u cO6Ru+346PuvdZcAW0MkKRZ31up+rbas8NP6Wv+NUOgmfqQ79gTyfsjBvf1d7VRSxaVS DzKGbxOH6r09b3WRIRfcfQGH+7Lm2V7PEs8rXeG54hunEd8O/OvT2gU8BqBbRS1sSqMW 1LZlqwTO+P0cfntTx0M+pLZirBr3rvU4n2plwyoURaz9+CtCskKb7CMZ+qw/o6cb8Ivs F9MQ==
X-Gm-Message-State: ALoCoQlTNbMZcrSRnlxsin90wd30QVPUYDyqhKK9l+DxTEF9DHqtwdo/2/pnc6s00oIUwnOGuWsS
X-Received: by 10.180.184.99 with SMTP id et3mr49400578wic.31.1408106608264; Fri, 15 Aug 2014 05:43:28 -0700 (PDT)
Received: from riaa ([2a00:801:e0:30:29a4:8d57:a5ae:3854]) by mx.google.com with ESMTPSA id ja13sm6507167wic.8.2014.08.15.05.43.26 for <ietf-http-wg@w3.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 15 Aug 2014 05:43:27 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"; format="flowed"; delsp="yes"
To: ietf-http-wg@w3.org
References: <38BD57DB-98A9-4282-82DD-BB89F11F7C84@mnot.net> <4851.1408094168@critter.freebsd.dk> <EB5B7C64-165B-48F1-94FF-1354E917A10F@mnot.net>
Date: Fri, 15 Aug 2014 14:43:25 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Martin Nilsson <nilsson@opera.com>
Organization: Opera Software
Message-ID: <op.xkmwanaliw9drz@riaa>
In-Reply-To: <EB5B7C64-165B-48F1-94FF-1354E917A10F@mnot.net>
User-Agent: Opera Mail/12.16 (Linux)
Received-SPF: pass client-ip=74.125.82.178; envelope-from=nilsson@opera.com; helo=mail-we0-f178.google.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-2.719, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1XIGrL-0007Oj-8v 687969708556153234abcfaea6a7dae8
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 and Pervasive Monitoring
Archived-At: <http://www.w3.org/mid/op.xkmwanaliw9drz@riaa>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26613
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 Fri, 15 Aug 2014 13:25:36 +0200, Mark Nottingham <mnot@mnot.net> wrote: > Hi PHK, > > On 15 Aug 2014, at 7:16 pm, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: >> Straw-man: >> ---------- >> >> http:/ can use TLS with *arbitrarily weak* crypto algorithms, >> and no authentication, and it is treated *exactly* like >> HTTP/1.1 plaintext by browsers. >> >> https:/ uses authenticated TLS with strong crypto, as today, >> and indicates this with the well-known changes in browser >> behaviour. > > It sounds like you're proposing that we allow weaker ciphersuites for > the Opp-Sec draft. > > That hasn't been discussed explicitly before IIRC, but it shares an > issue that we did previously discuss; if you're not authenticating the > Opp-Sec traffic, you want it to look as much like "real" TLS traffic as > possible, so that an attacker doesn't know which connections it can MITM > without being caught. What you can do in an MITM scenario isn't really relevant to PM. It's still harder to MITM weak TLS than clear text. I think it is more worrisome having the weak ciphers in there at all, as it opens up for bad configurations and downgrade attacks of https connections. /Martin Nilsson -- Using Opera's mail client: http://www.opera.com/mail/
- HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Amos Jeffries
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- RE: HTTP/2 and Pervasive Monitoring K.Morgan
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Eliot Lear
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Martin Nilsson
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- RE: HTTP/2 and Pervasive Monitoring Albert Lunde
- Re: HTTP/2 and Pervasive Monitoring Cory Benfield
- Re: HTTP/2 and Pervasive Monitoring Erik Nygren
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Roland Zink
- Re: HTTP/2 and Pervasive Monitoring Martin Thomson
- Re: HTTP/2 and Pervasive Monitoring Brian Smith
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Eliot Lear
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Stephen Farrell
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Roland Zink
- Re: HTTP/2 and Pervasive Monitoring Stephen Farrell
- Re: HTTP/2 and Pervasive Monitoring Amos Jeffries
- Re: HTTP/2 and Pervasive Monitoring Eliot Lear
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Ilari Liusvaara
- Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Martin Thomson
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Martin Thomson
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp