Re: [perpass] perens-perpass-appropriate-response-01

Bruce Perens <bruce@perens.com> Wed, 04 December 2013 23:41 UTC

Return-Path: <bruce@perens.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9281ADF59 for <perpass@ietfa.amsl.com>; Wed, 4 Dec 2013 15:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.177
X-Spam-Level:
X-Spam-Status: No, score=-1.177 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RP_MATCHES_RCVD=-0.001] 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 P_1rCyVw9kSb for <perpass@ietfa.amsl.com>; Wed, 4 Dec 2013 15:41:25 -0800 (PST)
Received: from alchemy.perens.com (alchemy.perens.com [206.221.219.26]) by ietfa.amsl.com (Postfix) with ESMTP id EBF231AD948 for <perpass@ietf.org>; Wed, 4 Dec 2013 15:41:24 -0800 (PST)
Received: from [192.168.18.131] (mail.a10networks.com [12.207.16.167]) by alchemy.perens.com (Postfix) with ESMTPSA id 056CB50008A for <perpass@ietf.org>; Wed, 4 Dec 2013 15:41:22 -0800 (PST)
Message-ID: <529FBDA6.9030100@perens.com>
Date: Wed, 04 Dec 2013 15:41:26 -0800
From: Bruce Perens <bruce@perens.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: perpass@ietf.org
References: <E2DA1477-C86E-441E-A33D-D47A0D67AFF3@iab.org> <EF9BD1E4-6EF3-4035-AC4E-1A2D3CADE615@mnot.net> <529E8494.7000806@perens.com> <20131204111309.GB11727@nic.fr> <529F61D8.6030105@perens.com> <20131204171207.GC19914@thunk.org> <529F63C0.3040804@perens.com> <529F88AC.3090904@appelbaum.net> <529F90A0.8000706@perens.com> <CFE20C30-34F4-4252-840E-E9CB5182BD26@fugue.com>
In-Reply-To: <CFE20C30-34F4-4252-840E-E9CB5182BD26@fugue.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] perens-perpass-appropriate-response-01
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 23:41:26 -0000

On 12/04/2013 03:27 PM, Ted Lemon wrote:
As to the question of encryption generally, nobody questions (I hope) that we want our transactions with banks to be secure.
And this is a solved problem except for the fact that they tend to get unencrypted laptops stolen with our data. Which we can't solve for them.
I think it's generally accepted that what videos we watch is private (there's a federal law in the U.S. making it illegal for video stores to give out that information).
They are private, and encrypted, but the encryption doesn't protect us. It only "protects" the video provider who believes that the whole internet will run away with their content if we are not forcibly restrained. If it works at all.

 They make it too easy for _anybody_ to eavesdrop, and to use the information they acquire whilst eavesdropping in really nefarious ways (e.g. the watering hole attack someone referred to recently).
So, build browsers that request https preferentially. Publish that as a recommendation. But please don't lock everyone into your solution.

    Thanks

    Bruce