IETF Logo Mail Archive

Re: [openpgp] "OpenPGP Simple"

Nicholas Cole <nicholas.cole@gmail.com> Tue, 17 March 2015 13:41 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 BBE3C1A03A8 for <openpgp@ietfa.amsl.com>; Tue, 17 Mar 2015 06:41:47 -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 EwRKTP6zHTkx for <openpgp@ietfa.amsl.com>; Tue, 17 Mar 2015 06:41:46 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (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 774241A00BE for <openpgp@ietf.org>; Tue, 17 Mar 2015 06:41:46 -0700 (PDT)
Received: by wibg7 with SMTP id g7so63595109wib.1 for <openpgp@ietf.org>; Tue, 17 Mar 2015 06:41:45 -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=BqpPNlio5SPmp11H2vP74T3Yv1uFjnx/ey7rj+SIUQY=; b=wXwmpM+FMWKDNk4XqMo3RtNIRfAF5l6oKSHqM9b9CaxplVemecXPc5Ms3kqbt8SdDU 3NSNj5l6m7lmPd5ZO4V9GldpNOmJh5Xaoo2/qENCVfYgBVu9gPEAg5UhGLyy8q6i9e5u ZXd+eJlOclP2BUBH9JleoY+DCFTJnlJHUDpLHDEO7k9d6ZjE3fn7IWIx3bQjGtgeQLLN 03LICJFiC0wtCF/lJ6Adr8bi+srr4NWXATOJVvoEWjEbYxCrSxmnympbShZdLyhHp8Ly tIFGrIa7DE+3+or94VXfYPOjqUvUotT6hukgk+kx9Wi7CQqgRzKF2xibPoyNWSVPn5TI tccg==
MIME-Version: 1.0
X-Received: by 10.194.222.197 with SMTP id qo5mr130575048wjc.142.1426599705267; Tue, 17 Mar 2015 06:41:45 -0700 (PDT)
Received: by 10.194.162.6 with HTTP; Tue, 17 Mar 2015 06:41:45 -0700 (PDT)
In-Reply-To: <CAHRa8=U-VBGYV0-+MWtvmUAGjh-7X795JLF+hDqDJZ=u79ioQg@mail.gmail.com>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB3811@uxcn10-5.UoA.auckland.ac.nz> <CAHBU6itMP3-wUGF3DAO_wZKwKJPWd=9g8g4GZ=hvnamkqJX55w@mail.gmail.com> <CAHRa8=U-VBGYV0-+MWtvmUAGjh-7X795JLF+hDqDJZ=u79ioQg@mail.gmail.com>
Date: Tue, 17 Mar 2015 13:41:45 +0000
Message-ID: <CAAu18hfbLv7MaaPTGm+fh3qwUm6Uzu43N3Y5nPASJYvGHDS8vQ@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/D7K4fRFrJU82iz_k97HOJsjDzbs>
Subject: Re: [openpgp] "OpenPGP Simple"
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: Tue, 17 Mar 2015 13:41:47 -0000

On Tue, Mar 17, 2015 at 12:53 PM, Wyllys Ingersoll <wyllys@gmail.com> wrote:
>
>
> On Tue, Mar 17, 2015 at 3:03 AM Tim Bray <tbray@textuality.com> wrote:
>>
>> I have repeatedly found it useful, even in recent times, to cut/paste
>> ASCII-armored messages on my mobile. Am I a Neanderthal?
>
>
> No!  This was exactly my first thought also. ASCII Armor format is extremely
> useful for passing the messages from app-to-app via the system clipboard
> using copy-and-paste.  As a mobile PGP developer, there are situations where
> this is the most convenient way to move the PGP message/key from a non-PGP
> enabled app (like most standard mobile mail clients) and into an app that
> can decode/decrypt it correctly.
>
> If ASCII Armor is to be deprecated, I would hope that we at least replace it
> with something else that can be easily copied-and-pasted.

I do hope (more generally) that this new spec does not seek change for
change's sake.

Things that are (or are likely to be) a security flaw should be
corrected, and some things that make the spec hard to implement should
be streamlined.  Features that are no longer used should be removed.
That's all.

v2.23.0 | Report a Bug | By Email