Re: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 03 July 2016 00:24 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6129312B026 for <openpgp@ietfa.amsl.com>; Sat, 2 Jul 2016 17:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CMTl2uc4z7V8 for <openpgp@ietfa.amsl.com>; Sat, 2 Jul 2016 17:24:05 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 B7C6E128874 for <openpgp@ietf.org>; Sat, 2 Jul 2016 17:24:05 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id e3so40396950qkd.0 for <openpgp@ietf.org>; Sat, 02 Jul 2016 17:24:05 -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:from:date:message-id :subject:to:cc; bh=OV7YdPFs5U2akjH3DHE6boynhw/UnvjXuZUS0qQoof8=; b=V8RBZZ5rbb8z3NxQFtFjPr84p9+sWOEeRBojUXfrzd0vsTYvwRRCzDkatKnZ5WEAhI 8JSpmmb3UjBelJKqTDlRin+OSc+WwVk/DF56J97CD7AyuHHi9Sr9sn8ruOKYPV88zX95 uQga0NAK8e7OiUjxeoxImTZcI8lgegek7QEcmtOD12jOrDf+H02XSa1II/4/PIzmJ+cZ KhzhrCDYWXv2BROBJEmKHVFzl0YuJipb3OoFbo4xy26dTIa3tjpKfOegjQMIC29BDu2j jVTkAaatQZqMeYLfpvRRwpBFU/VHy/IXxgPk2FMVDDyw+NChN8mD0bDsBt50qg29iqJn zeHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OV7YdPFs5U2akjH3DHE6boynhw/UnvjXuZUS0qQoof8=; b=do81p26yHMCmy9zZwpPV5yrsCaBuOwS4vUXvGu5vk+3yb3CGF/sGf97D+Aa+3vGQJM 7OF+cGD81tRqG45o1vn+oD5y1dZSJhX3+BkzSsd1VSxKT3BjF20D3oTbg9nzBaob2uzG 7s6AxRWq5wZ7YsuTzYMJ1PBvQggs5ZEFpRUy7zUCBb7h6iJoWCxalWTBq7yPDilw6MWs ouRlITwJwWZc/aFs/uin3NsBHGoqSP6iosqOEa1n9MhmNmS+D3+4p15Srd8SjCi6lw7M N5+uQKJ62SP/17ZAsNOLdI8Kc6lVQHPL+ZhqGzrByO5T8Qicb/LIe1UgAo/joSo6Ht0C oyag==
X-Gm-Message-State: ALyK8tJnvMg9dCXbZFaxiAlRInaNyJvkK6/YOLEJVL9oSUNx/C27SpLUf8Xu2r66ocggFo7Wg2yAixJuEqj94A==
X-Received: by 10.55.69.69 with SMTP id s66mr7712672qka.117.1467505444915; Sat, 02 Jul 2016 17:24:04 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.55.16.106 with HTTP; Sat, 2 Jul 2016 17:24:04 -0700 (PDT)
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C73F4CB8706@uxcn10-5.UoA.auckland.ac.nz>
References: <20160701153304.332d2c95@pc1> <sjmwpl5qtqy.fsf@securerf.ihtfp.org> <CAMm+LwjGZeZTpUjOp_McDrp6cMQQn=Sy6Wp+Ti5M--V4vnMDqw@mail.gmail.com> <9A043F3CF02CD34C8E74AC1594475C73F4CB8706@uxcn10-5.UoA.auckland.ac.nz>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 2 Jul 2016 20:24:04 -0400
X-Google-Sender-Auth: rvoz3uHQ44Jj9s5qYmUm0dkQeXM
Message-ID: <CAMm+LwhoaRCqp+-K4aGq9ALAh0bctYnOGRzYQSm5VA5RLVCaNg@mail.gmail.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Content-Type: multipart/alternative; boundary=001a1148a342c00f930536b03cac
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/_UKLF3yauczd5Nt_NS4AccXPM4M>
Cc: =?UTF-8?Q?Hanno_B=C3=B6ck?= <hanno@hboeck.de>, IETF OpenPGP <openpgp@ietf.org>, Derek Atkins <derek@ihtfp.com>
Subject: Re: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 03 Jul 2016 00:24:07 -0000

On Sat, Jul 2, 2016 at 11:08 AM, Peter Gutmann <pgut001@cs.auckland.ac.nz>
wrote:

> Phillip Hallam-Baker <phill@hallambaker.com> writes:
>
> >I have wanted this for a long time. there are actually three separate
> >problems to be solved.
> >
> >1) How to make S/MIME work with OpenPGP credentials
> >
> >2) How to make OpenPGP work with S/MIME credentials
> >
> >3) How to merge the two specifications into one.
>
> The first two are pretty easy, I've been doing that for years.  For S/MIME,
> use the subjectKeyIdentifier form of the key ID.  For PGP, use an
> issuerAndSerialNumber in a type-and-value subpacket.
>
> The third is impossible.  While at an abstract level PGP and S/MIME do the
> same thing, the bit-bagging formats used to encode the abstraction are
> completely incompatible.  You can't make them compatible without either
> moving
> S/MIME to the PGP format or PGP to the S/MIME format.  I can't see either
> of
> those happening...


​
That would clearly be impossible if it was what was being proposed.

What I am suggesting is rather different, A new application for managing
encrypted content, Word, Powerpoint, PDF, etc. that has crypto designed
into the metal and also provides a messaging capability.

I am suggesting Blu Ray, not trying to develop adapters to play VHS on
Betamax.
​