Re: [perpass] perpass: what next?

Mike Liebhold <mnl@well.com> Mon, 04 May 2015 19:22 UTC

Return-Path: <mnl@well.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 336451ACE65 for <perpass@ietfa.amsl.com>; Mon, 4 May 2015 12:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level:
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, 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 QxrskUzUAjJQ for <perpass@ietfa.amsl.com>; Mon, 4 May 2015 12:22:31 -0700 (PDT)
Received: from newsmtp.well.com (newsmtp.well.com [107.20.247.102]) by ietfa.amsl.com (Postfix) with ESMTP id D5D791A8AC4 for <perpass@ietf.org>; Mon, 4 May 2015 12:22:30 -0700 (PDT)
Received: from zimbra.well.com (zimbra.well.com [10.69.72.164]) by newsmtp.well.com (8.14.3/8.14.3) with ESMTP id t44JMT22031891 for <perpass@ietf.org>; Mon, 4 May 2015 12:22:29 -0700
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.well.com (Postfix) with ESMTP id 376994010FC0 for <perpass@ietf.org>; Mon, 4 May 2015 12:22:30 -0700 (PDT)
Received: from zimbra.well.com ([127.0.0.1]) by localhost (zimbra.well.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SzZBa55vNbmD for <perpass@ietf.org>; Mon, 4 May 2015 12:22:29 -0700 (PDT)
Received: from MLiebhold.local (unknown [199.73.113.19]) by zimbra.well.com (Postfix) with ESMTPSA id 469EA4010FC1 for <perpass@ietf.org>; Mon, 4 May 2015 12:22:29 -0700 (PDT)
Message-ID: <5547C6EF.8030001@well.com>
Date: Mon, 04 May 2015 12:22:23 -0700
From: Mike Liebhold <mnl@well.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: perpass@ietf.org
References: <5530EEAB.5050601@cs.tcd.ie> <CACsn0cn7sY8MFCumUknXfqPWqELUtLdyh55Z=av-0NSbMb3xYw@mail.gmail.com> <CAFJuDmMT9rgjLx6JhBKa9NNiNCpFeYWMxB13TMYL+g2A0JjTOg@mail.gmail.com> <20150421165947.GA3690@lo.psyced.org>
In-Reply-To: <20150421165947.GA3690@lo.psyced.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/nWZ-DUYeC_afVWHJeJI8k8kJc_o>
Subject: Re: [perpass] perpass: what next?
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: Mon, 04 May 2015 19:22:32 -0000

There are lots of highly relevant clues on what Perpass group might want 
to tackle next in this long summary of Ed Snowden's recent video-talk 
with cryptographers  at Princeton:

https://www.lightbluetouchpaper.org/

" ... Yesterday Ed Snowden spent four hours with a group of 
cryptographers from industry and academia, of which I was privileged to 
be one. The topic was the possible and likely countermeasures, both 
legal and technical, against state surveillance. Ed attended as the 
“Snobot”, a telepresence robot that let him speak to us, listen and move 
round the room, from a studio in Moscow. As well as over a dozen 
cryptographers there was at least one lawyer and at least one journalist 
familiar with the leaked documents. Yesterday’s meeting was under the 
Chatham House rule, so I may not say who said what; any new disclosures 
may have been made by Snowden, or by one of the journalists, or by one 
of the cryptographers who has assisted journalists with the material.

  [snip]  . . . "