Return-Path: <pgut001@cs.auckland.ac.nz>
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 A3B5D12D1E6
 for <openpgp@ietfa.amsl.com>; Sun,  3 Jul 2016 21:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.626
X-Spam-Level: 
X-Spam-Status: No, score=-5.626 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=auckland.ac.nz
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 vIFTrcZC7zgt for <openpgp@ietfa.amsl.com>;
 Sun,  3 Jul 2016 21:14:44 -0700 (PDT)
Received: from mx4.auckland.ac.nz (mx4.auckland.ac.nz [130.216.125.248])
 (using TLSv1.2 with cipher RC4-SHA (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id C8BBE12B01B
 for <openpgp@ietf.org>; Sun,  3 Jul 2016 21:14:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
 d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail;
 t=1467605683; x=1499141683;
 h=from:to:subject:date:message-id:references:in-reply-to:
 content-transfer-encoding:mime-version;
 bh=bfAwzibSsvMUtQJPJbdSMOSQ0RwOM2u9uNZ2Ih4agoM=;
 b=svE2wQbY2a7zzx0TWQN3Ha/y/m6uFW45SLEiW6uM7NUhA9t4thTjFa+j
 wEEaSYcdyLNl1BxHRxhxN/42VoXtB1S4JCvtUlzhFICx4hMf0eFsPw2t1
 a0dw32RhmR3KtiVYyPdxHu0mS3XbwK19Ab4vk5Y81G6y/jpVeaTXi4ZZH
 01u3LLbg6iPYxk9WOWqSN9pCNY4wiIfV5KWGJakiH9RaTvrKi3pHObCR1
 7DjNeTwIsb84g1TiJ1h6LUS0LO113n19MKauX2BMINLLW5YE2Swb0P71R
 qSAm/COwWTziMPaJXpXJi+FRRnfV/DdT1vctLh8MrnZwRlPaJoAYVvyD1 Q==;
X-IronPort-AV: E=Sophos;i="5.26,573,1459771200"; d="scan'208";a="94826677"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.125 - Outgoing - Outgoing
Received: from uxchange10-fe3.uoa.auckland.ac.nz ([130.216.4.125])
 by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 04 Jul 2016 16:14:40 +1200
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.93]) by
 uxchange10-fe3.UoA.auckland.ac.nz ([169.254.143.234]) with mapi id
 14.03.0266.001; Mon, 4 Jul 2016 16:14:40 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Andrey Jivsov <openpgp@brainhub.org>, "openpgp@ietf.org" <openpgp@ietf.org>
Thread-Topic: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?
Thread-Index: AQHR050jpR81NF3KlE2UhFa6MyYJKaAGlDWAgAEQVZj//z2nAIAAy69z
Date: Mon, 4 Jul 2016 04:14:39 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4CB9814@uxcn10-5.UoA.auckland.ac.nz>
References: <20160701153304.332d2c95@pc1>,
 <874m86xq04.fsf@alice.fifthhorseman.net>
 <9A043F3CF02CD34C8E74AC1594475C73F4CB97D2@uxcn10-5.UoA.auckland.ac.nz>,
 <5779E086.9000506@brainhub.org>
In-Reply-To: <5779E086.9000506@brainhub.org>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.6.2.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/8luhIMfoYIYvuSxCT7bN2IyzX-8>
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: Mon, 04 Jul 2016 04:14:47 -0000

Andrey Jivsov <openpgp@brainhub.org> writes:=0A=
=0A=
>One issue with storing OpenPGP KeyID in X.509 Subject Key Identifier (SKI)=
 is=0A=
>that over the last decade and earlier popular S/MIME clients were not usin=
g=0A=
>SKI to identify a recipient. Instead, they were using the X.509 cert's Iss=
uer=0A=
>and SN. Therefore, one will have to encode OpenPGP keyID into the SN of th=
e=0A=
>X.509 cert to be able to locate the OpenPGP key later from the encrypted=
=0A=
>S/MIME message. This works if the ecosystem owns an issuing X.509 Sub-CA, =
so=0A=
>that it's possible to control the SNs.=0A=
=0A=
We'd really need to get more data on what can handle sKID, since in my case=
=0A=
the use is all closed environments (banking, embedded, SCADA, etc) it's eas=
y=0A=
enough to simply specify that the implementation needs to support sKID but=
=0A=
there's no current data (that I know of) on general support.  In any case I=
=0A=
think getting a small number of implementations to support sKID is going to=
 be=0A=
vastly easier than asking CAs to put PGP IDs into certs.=0A=
=0A=
In any case it doesn't cost anything to put the sKID/iAndS details into the=
=0A=
spec, and if you want it you've at least got an interoperable way of doing =
it.=0A=
=0A=
Peter.=0A=

