Re: [perpass] Howdy!

Phil Karn <karn@philkarn.net> Fri, 20 September 2013 14:50 UTC

Return-Path: <karn@philkarn.net>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E25D21F9B35 for <perpass@ietfa.amsl.com>; Fri, 20 Sep 2013 07:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9Hu32gHxJ7x for <perpass@ietfa.amsl.com>; Fri, 20 Sep 2013 07:50:18 -0700 (PDT)
Received: from homer.ka9q.net (homer.ka9q.net [75.60.237.89]) by ietfa.amsl.com (Postfix) with ESMTP id AF7A721F9B28 for <perpass@ietf.org>; Fri, 20 Sep 2013 07:50:15 -0700 (PDT)
Received: from ip-64-134-136-120.public.wayport.net ([64.134.136.120] helo=[192.168.5.15]) by homer.ka9q.net with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <karn@philkarn.net>) id 1VN228-0006Bm-9p; Fri, 20 Sep 2013 07:50:12 -0700
Message-ID: <523C6083.6020703@philkarn.net>
Date: Fri, 20 Sep 2013 07:49:39 -0700
From: Phil Karn <karn@philkarn.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: perpass@ietf.org
References: <CAOHm=4ujOYTHO63EFWMYJBgxUWq00zezYKAJ8B4Vgf_C=xRRVg@mail.gmail.com> <5224DF25.60503@cs.tcd.ie> <7C92613E-33E8-48A6-A152-E9DBB29DEC04@softarmor.com> <522A328A.5060008@cs.tcd.ie> <522E17F9.4000206@bbn.com> <522F685B.8040106@gmx.net> <20130910185544.GF29237@thunk.org> <5232D366.1000803@appelbaum.net> <m28uz0fw83.wl%randy@psg.com>
In-Reply-To: <m28uz0fw83.wl%randy@psg.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] Howdy!
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <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: Fri, 20 Sep 2013 14:50:24 -0000

On 09/13/2013 10:49 AM, Randy Bush wrote:

> i might go further.  having some protocols in the clear allows the
> attacker to better focus their efforts on what is encrypted.  also,
> though some data themselves might not require privacy, the nature of
> the conversation may facilitate traffic analysis.

Yes. We've seen indications that the NSA stores all encrypted traffic
for a rainy day, so the more chaff we can generate the sooner the NSA
will have to look for new real estate in Utah.

--Phil