Re: [Endymail] What are the problems?

Elijah Sparrow <elijah@leap.se> Sun, 07 September 2014 18:16 UTC

Return-Path: <elijah@leap.se>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ED21A064B for <endymail@ietfa.amsl.com>; Sun, 7 Sep 2014 11:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, UNPARSEABLE_RELAY=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 z-Q4SMkYorLW for <endymail@ietfa.amsl.com>; Sun, 7 Sep 2014 11:16:32 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 864581A063C for <endymail@ietf.org>; Sun, 7 Sep 2014 11:16:32 -0700 (PDT)
Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 5856252658 for <endymail@ietf.org>; Sun, 7 Sep 2014 11:16:31 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: elijah) with ESMTPSA id 307D942A6F
Message-ID: <540CA101.2010000@leap.se>
Date: Sun, 07 Sep 2014 11:16:33 -0700
From: Elijah Sparrow <elijah@leap.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: endymail@ietf.org
References: <CACsn0cmmpg3VAEdVdLsBRJUkHnnPJ7fAXBaH4oVpRHm1LdK0sw@mail.gmail.com>
In-Reply-To: <CACsn0cmmpg3VAEdVdLsBRJUkHnnPJ7fAXBaH4oVpRHm1LdK0sw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.98.4 at mx1
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/XFmva7l85VvcVuzj_FmICsuSvp4
Subject: Re: [Endymail] What are the problems?
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 18:16:34 -0000

On 09/07/2014 10:55 AM, Watson Ladd wrote:

> Let's back up from spam.

I have attempted to enumerate the major issues involved in end-to-end
email in this report:

https://github.com/OpenTechFund/secure-email

It also includes a brief summary of each of the major projects working
on 'new generation' end-to-end encrypted email (in general, these
projects all seek something less difficult, more automatic, and
sometimes with greater security than existing openpgp or s/mime).

Phillip may note that the report does not include PPE. I haven't had the
chance to update the report with a PPE entry since PPE was posted. Pull
requests welcome.

The darkmail entry is also out of date, now that they have a new
architecture.

-elijah