[perpass] A proposal for developing PRISM-Proof email
Phillip Hallam-Baker <hallam@gmail.com> Fri, 20 September 2013 18:58 UTC
Return-Path: <hallam@gmail.com>
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 D15DD21F9D98 for <perpass@ietfa.amsl.com>; Fri, 20 Sep 2013 11:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 GaiH0adDmFXk for <perpass@ietfa.amsl.com>; Fri, 20 Sep 2013 11:58:59 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9762F21F9D95 for <perpass@ietf.org>; Fri, 20 Sep 2013 11:58:58 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id gx14so683855lab.9 for <perpass@ietf.org>; Fri, 20 Sep 2013 11:58:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vq2FkiEVZsQFEJqZPzgb6GCMnOYlhSRxQc/7PYRsi1Q=; b=jPC9CTrGZcYqJVQMCHnwn1kZWDFt1NW30FFqjtVO06cWw8RqVw12ZMZ4jUHu/X00cX UF/8NST8TxXcgV7mv0I1EHg6jMWg6OnvO2LfQV8SOCdP4bBfQlFEmW5jAb0o3MtKLqw1 IN3C9fooKa5bq/k2ZMOquQccHdLTw6oKf+zulTB7t38AEPS2ThxAZHlKd2qSwqWhgs8x KMqLXyzuPny2YcFhPfXKCEl8f/wst/Rey5cb2C7r+FNMZfzhbJ7CZzkrhhOom6sdxJq+ 4z7bZbQlaHTYlUTOHj0K7PsnG1DqAa/MIHJMERxTrIWDUUK7hduE08mpxzbllbhar5pr 6RVw==
MIME-Version: 1.0
X-Received: by 10.112.129.163 with SMTP id nx3mr91733lbb.60.1379703537521; Fri, 20 Sep 2013 11:58:57 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Fri, 20 Sep 2013 11:58:57 -0700 (PDT)
Date: Fri, 20 Sep 2013 14:58:57 -0400
Message-ID: <CAMm+Lwj8OSxsLG1yLYwbTaxd4stt=RryvRE2krFkYuUNh8Mu8g@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: perpass <perpass@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b3a7f663fda0304e6d5433e"
Subject: [perpass] A proposal for developing PRISM-Proof email
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 18:58:59 -0000
We need an email security infrastructure and recent events demonstrate that the infrastructure we develop needs to be proof against PRISM-class attacks. By PRISM-class I mean an attack that attempts pervasive surveillance with budgets in excess of $100 million rather than the PRISM program in particular. Neither OpenPGP nor S/MIME is capable of providing protection against this class of attack because they are not widely enough used. We can only hope for these to be useful if at least 5% of Internet users start sending mail securely. But while the legacy protocols are not sufficient, 95% of the existing work is fine and does not need to be repeated although there may be some details of execution that can be improved. The part that is going to need new research is in the area of trust models. As someone who has seen the documents said to me this week, given a choice between A and B, the NSA does both. We have to do the same. Rather than have a pointless argument about whether Web 'o Trust or PKIX is the way to go, let everyone do both. Let people get a certificate from a CA and then get it endorsed by their peers: belt and braces. The idea in this draft is to split up the problem space so that people who know email clients can write code to support any of the research ideas that might be proposed and any of the research ideas can be used with any of the mail clients that have been enabled. The draft is to be found at: http://www.ietf.org/id/draft-hallambaker-prismproof-dep-00.txt -- Website: http://hallambaker.com/
- [perpass] A proposal for developing PRISM-Proof e… Phillip Hallam-Baker
- Re: [perpass] A proposal for developing PRISM-Pro… Bjoern Hoehrmann
- Re: [perpass] A proposal for developing PRISM-Pro… Adam Caudill
- Re: [perpass] A proposal for developing PRISM-Pro… Leif Johansson
- Re: [perpass] A proposal for developing PRISM-Pro… Jon Callas
- Re: [perpass] A proposal for developing PRISM-Pro… Phillip Hallam-Baker
- Re: [perpass] A proposal for developing PRISM-Pro… Scott Brim
- Re: [perpass] A proposal for developing PRISM-Pro… Leif Johansson
- Re: [perpass] A proposal for developing PRISM-Pro… Paul Kyzivat
- Re: [perpass] A proposal for developing PRISM-Pro… SM
- Re: [perpass] A proposal for developing PRISM-Pro… Bjoern Hoehrmann
- Re: [perpass] A proposal for developing PRISM-Pro… ned+perpass
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Stephen Farrell
- Re: [perpass] A proposal for developing PRISM-Pro… Randy Bush
- Re: [perpass] A proposal for developing PRISM-Pro… Dave Crocker
- Re: [perpass] A proposal for developing PRISM-Pro… Phillip Hallam-Baker
- Re: [perpass] A proposal for developing PRISM-Pro… Carl Wallace
- Re: [perpass] A proposal for developing PRISM-Pro… Phillip Hallam-Baker
- Re: [perpass] A proposal for developing PRISM-Pro… Carl Wallace
- Re: [perpass] A proposal for developing PRISM-Pro… Phillip Hallam-Baker
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Bjoern Hoehrmann
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Bjoern Hoehrmann
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Leo Vegoda
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Leo Vegoda
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Leo Vegoda
- Re: [perpass] A proposal for developing PRISM-Pro… Stephen Farrell
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Mike Demmers
- Re: [perpass] A proposal for developing PRISM-Pro… Elijah Sparrow
- Re: [perpass] A proposal for developing PRISM-Pro… Phillip Hallam-Baker
- Re: [perpass] A proposal for developing PRISM-Pro… Richard Shockey