Re: [openpgp] saltpack on OpenPGP message format problems

Derek Atkins <derek@ihtfp.com> Fri, 12 February 2016 17:06 UTC

Return-Path: <derek@ihtfp.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 9B3641A7021 for <openpgp@ietfa.amsl.com>; Fri, 12 Feb 2016 09:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level:
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_ORG=0.611] autolearn=no
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 Fecj5ICuXfDt for <openpgp@ietfa.amsl.com>; Fri, 12 Feb 2016 09:06:53 -0800 (PST)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 621901A701C for <openpgp@ietf.org>; Fri, 12 Feb 2016 09:06:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 1E901E2036; Fri, 12 Feb 2016 12:06:21 -0500 (EST)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 26242-01; Fri, 12 Feb 2016 12:06:17 -0500 (EST)
Received: from securerf.ihtfp.org (IHTFP-DHCP-159.IHTFP.ORG [192.168.248.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail2.ihtfp.org (Postfix) with ESMTPS id D4E4BE2030; Fri, 12 Feb 2016 12:06:16 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1455296776; bh=h7oSP9IjOeZ28HMtqyGO5EouIdWEXHQt3e+Gw/17JVc=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=I3lDAZ5W+sLTDtnIhb19cG+20fbC4UBg1lsZOCQHQ+7M5rekGYRk/lYUZJI1QtOC3 l7n3fxfp4LgFmAhK5SaY7Ykf36HevDIHJEX8pSETM6xdoivle+8n9X/GrAVO8P+M+G K1I/glBt5nuhfHD4YpjR7MOzPX1+49vJzdixw/+Q=
Received: (from warlord@localhost) by securerf.ihtfp.org (8.15.2/8.14.8/Submit) id u1CH6FGa028819; Fri, 12 Feb 2016 12:06:15 -0500
From: Derek Atkins <derek@ihtfp.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
References: <56BB0308.8020504@iang.org> <20160210160641.GA3090@singpolyma-liberty> <9A043F3CF02CD34C8E74AC1594475C73F4BED18C@uxcn10-5.UoA.auckland.ac.nz> <87lh6rbp5n.fsf@vigenere.g10code.de> <9A043F3CF02CD34C8E74AC1594475C73F4BEE527@uxcn10-5.UoA.auckland.ac.nz>
Date: Fri, 12 Feb 2016 12:06:15 -0500
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C73F4BEE527@uxcn10-5.UoA.auckland.ac.nz> (Peter Gutmann's message of "Fri, 12 Feb 2016 13:51:11 +0000")
Message-ID: <sjm60xt3lko.fsf@securerf.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/obswTIwa7TCsEwT7Sbm2PpXZcjw>
Cc: Stephen Paul Weber <singpolyma@singpolyma.net>, Werner Koch <wk@gnupg.org>, "openpgp@ietf.org" <openpgp@ietf.org>, ianG <iang@iang.org>
Subject: Re: [openpgp] saltpack on OpenPGP message format problems
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 12 Feb 2016 17:06:54 -0000

Peter,

Peter Gutmann <pgut001@cs.auckland.ac.nz> writes:

> Werner Koch <wk@gnupg.org> writes:
>
>>How do you want to paste binary data into a contact web form or a Git commit
>>message?  The OpenPGP Armor makes this really easy and, fwiw, X.509 uses a
>>similar armoring technique.
>
> I dunno because that's not my area of expertise, but somehow every other
> software mechanism in existence has managed to get by without needing its own
> custom "ASCII armoring" (is there anything other than PGP that does this?), so
> I'm guessing it's a solved problem.

The only thing custom about PGP's ASCII Armor is the extra CRC.  I agree
that can probably be dropped, except of course there's the
backwards-compatibility issue.  As others have mentioned, there are
definitely reasons to keep *an* ascii armor format, especially for
key/certificate transit (ala an x509 csr/crt submission/retrieval).

>>Regarding PGP/MIME, it might be worth to consider dropping the need for the
>>ASCII armor in favor of standard MIME encoding.  This would also help to sort
>>out faulty PGP/MIME implementations.
>
> That would certainly help with usability, since 99.9% of the time it's
> completely redundant and better handled through other mechanisms.

For messages I agree, it's redundant in most current situations.

> Peter.

-derek
-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant