Re: [openpgp] Character encodings

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Wed, 18 March 2015 22:13 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7BF1A88FD for <openpgp@ietfa.amsl.com>; Wed, 18 Mar 2015 15:13:31 -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] 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 GgicZWiF3BKs for <openpgp@ietfa.amsl.com>; Wed, 18 Mar 2015 15:13:29 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by ietfa.amsl.com (Postfix) with ESMTP id 914831A88F0 for <openpgp@ietf.org>; Wed, 18 Mar 2015 15:13:29 -0700 (PDT)
Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 603FCF984; Wed, 18 Mar 2015 18:13:25 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 67246201BE; Wed, 18 Mar 2015 15:13:20 -0700 (PDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
In-Reply-To: <CAMm+LwgRhLZiHNd3sS6GrPWE4JuA3+mStvwBNOYowbgAOcw12A@mail.gmail.com>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB4B37@uxcn10-5.UoA.auckland.ac.nz> <CAMm+LwgRhLZiHNd3sS6GrPWE4JuA3+mStvwBNOYowbgAOcw12A@mail.gmail.com>
User-Agent: Notmuch/0.18.2 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu)
Date: Wed, 18 Mar 2015 18:13:20 -0400
Message-ID: <87y4mugdj3.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/Gge1yNoggJ-zbWWU1_buSw-pkEQ>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
Subject: Re: [openpgp] Character encodings
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2015 22:13:31 -0000

On Wed 2015-03-18 09:08:26 -0400, Phillip Hallam-Baker wrote:
> This makes it a lot easier for folk who have an S/MIME implementation to
> add OpenPGP support. It is also the approach that has been debugged and is
> known to work with legacy mail infrastructure.
>
> One of the main challenges with end-to-end mail is Webmail which is now
> used by most mail users. It is possible to get end-to-end to work with
> webmail on the receiver side but it requires a mechanism that allows the
> server to say 'here is an encrypted blob in format X, decrypt it with the
> key you hold locally and present it to the user'. On the sender side you
> need an editing widget that can be called out that will deliver the content
> to be encrypted.
>
> That is going to be easiest to get from the browser community if there is
> least variation between the E2E email formats.

Please take a look at the "end-to-end" website API:

 https://github.com/google/end-to-end/wiki/Website-API

I don't think it covers all the cases you describe, but it's nicely
concise at the moment, and maybe just needs a few tweaks to be able to
reach some of the mechanisms you're looking for.

      --dkg