Re: [Endymail] Why S/MIME and OpenPGP ecosystems fall short

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 04 June 2015 18:19 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 6D30D1A87C1 for <endymail@ietfa.amsl.com>; Thu, 4 Jun 2015 11:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] 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 dnH7MRk2JExW for <endymail@ietfa.amsl.com>; Thu, 4 Jun 2015 11:19:11 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7992E1A87BD for <endymail@ietf.org>; Thu, 4 Jun 2015 11:19:11 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 5BCF5FA0065; Thu, 4 Jun 2015 18:19:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1433441949; bh=IoZjyiB7dTG7va6kb9mbf+A/ua6Y62wOHagzYyiiHgY=; h=From:To:Subject:References:Date:From; b=g/9eKRODn75Lry1PeyG0fvlJljHlebgTQ/0z1A3RVTu5S9IlN0WfP+jpcY+FqP0FO Ci7Efp2cWig7NWJcep9TKBtf5RIGiSLd6po6FJ5VeAXU6r9JSWiujidyJxj4QZSBLM N6j09Wxnng9HZUYdviw1mGkgNE5Pw2/iuax7evIE=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1433441947-28872-28871/12/43; Thu, 4 Jun 2015 18:19:07 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: endymail@ietf.org, Michael Kjörling <michael@kjorling.se>
Message-Id: <4kJBhKBGz4D2R7baTFaYgRv+rNvp6FRmkxAQ7LKhNP4=.sha-256@antelope.email>
References: <CACsn0c=1RfwZF3-ynoaer=QkRXE56Mzwe1y50QQirW=GMBwvYA@mail.gmail.com> <20150603095917.GC25546@yeono.kjorling.se>
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Date: Thu, 04 Jun 2015 18:19:07 +0000
Archived-At: <http://mailarchive.ietf.org/arch/msg/endymail/6UdlvC1y3sApe-RBy-4EDmaRvoM>
Subject: Re: [Endymail] Why S/MIME and OpenPGP ecosystems fall short
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: Thu, 04 Jun 2015 18:19:14 -0000

If you have zero experience with textsecure, I suggest that you get 
some before you continue to talk about these things. Because textsecure 
is a messaging system with good crypto and good deployment, and that is 
rare enough to be worth learning from.

You cannot just say that 
textsecure ignores something and silently assume that that thing must 
be done, solved or supported: maybe ignoring that is precisely the key 
to wide deployment.

Arnt