Re: [openpgp] Character encodings

Nicholas Cole <nicholas.cole@gmail.com> Wed, 18 March 2015 09:42 UTC

Return-Path: <nicholas.cole@gmail.com>
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 6D3831A0162 for <openpgp@ietfa.amsl.com>; Wed, 18 Mar 2015 02:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 qs39PiIvSw7b for <openpgp@ietfa.amsl.com>; Wed, 18 Mar 2015 02:42:11 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C2EB1A0103 for <openpgp@ietf.org>; Wed, 18 Mar 2015 02:42:11 -0700 (PDT)
Received: by wggv3 with SMTP id v3so30157984wgg.1 for <openpgp@ietf.org>; Wed, 18 Mar 2015 02:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=kzodZLzRJSX+xjK67IUKJRhCaSbGZMY1oSGGd6hvkZ8=; b=BhkGrY5tQIJuMcJMxldYLviiyAyOSzOUFJ541mhjl+mdWQyY4USOVvdc0d4FSblg1r 6XM7LsKA/JQtHYV06hFLWIhjhSiL4NKbFPJQWoyKqdyAy0AcJbOyPHyzUuX/nl9hnrkk F9SoNjVLnM2/y9UzKvg8deXxS6VM0CKCdzdKN9u+kKRpMyqf9LehRGR1n4pmXH7NAoHM iHTRTjx87tppBrt1q27tZHX/0Ay2nFJ8+4C78i4fbT3/2RfJQpbBqz3769664lako4Gu xMUh8WkSJaNXMLkXzMYbroJVM+5e1k2z2tWbJBiYxiF6F3fsCRMk19bkOni+Tgv5PisS Ys3A==
MIME-Version: 1.0
X-Received: by 10.180.107.71 with SMTP id ha7mr5218598wib.23.1426671729949; Wed, 18 Mar 2015 02:42:09 -0700 (PDT)
Received: by 10.194.162.6 with HTTP; Wed, 18 Mar 2015 02:42:09 -0700 (PDT)
In-Reply-To: <87619y1xab.fsf@vigenere.g10code.de>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB4B37@uxcn10-5.UoA.auckland.ac.nz> <87619y1xab.fsf@vigenere.g10code.de>
Date: Wed, 18 Mar 2015 09:42:09 +0000
Message-ID: <CAAu18hdx5VOPSwb8=V58eM+2vKoP6mby-dKxC5Qk7H62=MKxHA@mail.gmail.com>
From: Nicholas Cole <nicholas.cole@gmail.com>
To: "openpgp@ietf.org" <openpgp@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/tnxaquk631jluYdEfaV6xohwGIA>
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 09:42:12 -0000

On Wed, Mar 18, 2015 at 9:15 AM, Werner Koch <wk@gnupg.org> wrote:
> On Wed, 18 Mar 2015 04:48, pgut001@cs.auckland.ac.nz said:
>
>>>> Just get rid of the notion of text. Make it be all binary. Push the
>>>> problem up a layer in the software stack -- they have to deal with it
>>>> anyway, and all OpenPGP can do is make it worse.
>>>
>>>+1
>>
>> +2.  The rest of the world has made do with the existing infrastructure for
>
> +3.  The text mode and the different interpretation on how to handle
> line endings has likely been the most troublesome experience for any
> implementation.  And it still does not work universally (the last LF
> problem).
>
> The drawback will be the loss of the easy to c+p clearsign method.  It
> might be replaced by something MIMEish to still allow for c+p.
>
>> (If all else fails, make the contents of the PGP message a MIME body like
>> S/MIME does, so the processing-flow is "MIME message" (S/MIME data) -> filter
>> implementing the crypto (in decoded, binary form) -> "MIME message"
>
> i.e. PGP/MIME without the requirement of using an armored message.
> Should be easy to implement in any MUA.

Wouldn't anything that can be cut and pasted essentially run in to
this problem? I do think there is still utility in having something
that is a "clearsign" (that is, human-readable even without OpenPGP
software) that can be easily cut and pasted.