Re: [openpgp] "OpenPGP Simple"

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 22 March 2015 14:05 UTC

Return-Path: <hallam@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 22C021A90E1 for <openpgp@ietfa.amsl.com>; Sun, 22 Mar 2015 07:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 bxLl90Rfpq7W for <openpgp@ietfa.amsl.com>; Sun, 22 Mar 2015 07:05:06 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (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 C6F171A90DB for <openpgp@ietf.org>; Sun, 22 Mar 2015 07:05:05 -0700 (PDT)
Received: by labto5 with SMTP id to5so9020300lab.0 for <openpgp@ietf.org>; Sun, 22 Mar 2015 07:05:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=WANqzPuYHgal41gF2mS1z2FBtNx0VoRtfbPI2vPjRD4=; b=MuJm0R6PSMKETdFtxPlZ8IYUdURLgDRGNO5I4AKGhdiSZBvpHN0gdHXqlAKBaHz3Rr zvm1xKm6NoIeT4CDkiv+4T+ulRWrQ/ETZmnGwy+Z/YGdH7SEEpC/74Sy/G2BmdlTbV+W OCIXdkdc2cfxvY7YDg58ZhdKf+0xZF8whw1QZZg/VW1NMDuLEKrgmjZSRmBjDwDv26bf M3IGwZvE637Ywuc0ZQc10GII9z+3kwTrMaJEwD+bzK0ef4Cm5bX7+jMWpXdY5Gz+vJBF T6O9pdEfBzf9iNlJl2tk1A8ArSghgT69c52/2GrLLkhLc7Ae8KJrafzHVAhG9j0wrSQe 1pYQ==
MIME-Version: 1.0
X-Received: by 10.152.120.8 with SMTP id ky8mr77054717lab.118.1427033104310; Sun, 22 Mar 2015 07:05:04 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.45.203 with HTTP; Sun, 22 Mar 2015 07:05:04 -0700 (PDT)
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C73AAFB984B@uxcn10-5.UoA.auckland.ac.nz>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB984B@uxcn10-5.UoA.auckland.ac.nz>
Date: Sun, 22 Mar 2015 10:05:04 -0400
X-Google-Sender-Auth: llaXZF2ECJjczNDh-v8egkJeA1Q
Message-ID: <CAMm+LwhA4OFqT1HTzzJNjC2fiSQ7++NNu9ZnLZyteAe87KcXug@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/EnVOpLRcrDUqrX3w4DngW1EyKUU>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
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: Sun, 22 Mar 2015 14:05:07 -0000

On Sun, Mar 22, 2015 at 9:54 AM, Peter Gutmann
<pgut001@cs.auckland.ac.nz> wrote:
> Derek Atkins <derek@ihtfp.com> writes:
>
>>Have you tried to have them read the CMS/PKIX set of specs??  And they still
>>think that 4880 is too complex??
>
> Having implemented both 3369 and 4880 (I'm not going to touch 5280 et al, no-
> one has that much asbestos), 3369 is much easier to work with.  The reason for
> this is that there's a single overall type (ContentInfo) for everything and
> then consistent subtypes (SignedData, EnvelopedData) within that, all
> collected together inside type-specific containers.  PGP OTOH is a series of
> packets with somewhat arbitrary fields (look at the literal-data packet for
> example), all concatenated together in a rather ad hoc order, which means you
> have to hand-craft parsing code for almost everything.  When a new type
> (AuthEnvelopedData) was added to CMS I just added an OID and a function
> pointer to the decoding table and a bit of glue code and I was done.  The PGP
> equivalent OTOH, MDC'd data... ugh.


I have also done a CMS a few times, it isn't a biggie. PKIX path math
certainly is, particularly if the insanity of policy constraints is
attempted. But CMS isn't that hard.

Even ASN.1 BER encoding isn't that difficult. The really horrible part
is having to do DER.